Reduce approval waiting

A controlled way to reduce waiting is to teach a policy which routine actions can proceed, while preserving review or automatic denial for everything else.

Start with real requests

1. Use an Ask User policy while you learn the commands your agents actually run.
2. Turn on Remember decisions in Approvals.
3. Approve a routine request and save the narrowest useful Allow List rule.
4. Deny an unwanted request and save an appropriate Deny List rule.
5. Review both lists under Policy and remove rules that are broader than intended.

Use Permissive when its common low-risk Allow List matches your workflow. Use Restrictive when you also want the shipped destructive patterns denied automatically.

Allow ordinary work while keeping blocks

If you want unmatched work to continue without asking, duplicate Restrictive and choose Allow by Default. Review every Deny List category before activating the copy. Anything missing from the Deny List will be allowed.

See Policies and default behavior for the complete duplication steps and the difference between the built-in presets.

Keep manual requests visible

Allow iOS notifications and test one unmatched harmless request. Add Apple Watch if you want a second place to respond. The current manual approval timeout is five minutes, and an unanswered request is denied rather than approved.

Avoid shortcuts that remove protection

• Allow All skips policy list checks.
• An Allow offline fallback applies when the service cannot be reached. It is not a response timer.
• Approve All can remember broad rules when Remember decisions is on.
• The active policy applies across your account, so a change intended for one agent can affect other connected agents.

After changing policy or notification settings, follow Verify your setup again with a harmless request.