Auto-approve

/config auto-approve <tool> on|off turns off the permission prompt for one specific tool going forward, applied across every future session on that machine, not just the one currently running.

See Permissions and safety for how this interacts with answering always at an individual prompt instead, which only lasts for the remainder of the current session rather than persisting.

This is the one setting on this page with real safety implications if set too broadly, so it is worth being deliberate about which specific tools you actually trust enough to skip review for entirely.

A reasonable starting posture is auto-approving bash only in projects with a test suite you already trust, and leaving write_file and edit_file unapproved by default even there, since those are the two tools that change source files directly rather than just running something.

Turning a tool's auto-approve back off is exactly as fast as turning it on, the same command with off in place of on, so there is no friction in reversing a decision once a project's circumstances change.