Common workflows

Reduce approval waiting

Auto-decide routine work without removing the safeguards that matter to you.

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 Block when you also want the shipped destructive patterns denied automatically.

Use Policy Rules for recurring kinds of actions

On an eligible Solo or Pro plan, Policy Rules can recognize a condition across different tool inputs. Start with a library rule, review its examples, and choose what should happen when it matches. An Allow rule must cover the whole action before it can approve it.

If a rule asks about too many harmless actions, add a non-matching example or refine its definition. Raising its match threshold also reduces matches, but may miss actions you wanted caught. Check the results after each change. A broad Allow List entry bypasses rule evaluation, so use it only when that is your intent.

Allow ordinary work while keeping blocks

If you want unmatched work to continue without asking, duplicate Restrictive Block and choose Allow by Default. Review every Deny List category before activating the copy. Enabled Policy Rules check actions left undecided by the Deny, Allow, and Ask Lists; the default allows anything left undecided.

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. Unanswered requests are denied by default. A policy can instead use an auto-approval veto window for ordinary requests; Ask rules still require your answer. Review Timeouts and offline fallback before changing it.

Avoid shortcuts that remove protection

  • Allow All skips both lists and Policy Rules.
  • 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.

Go out and grab a coffee

We'll ping you if your agents need you. Try Agent Approve free for 7 days.