Setting auto-approve ahead of time

If you already know, before a session even starts, that you want a given tool to run without asking, /config auto-approve <tool> on|off sets that in advance rather than waiting for the first prompt and answering always there.

This persists across future sessions too, not just the current one, which makes it the right choice for a tool you have fully decided you trust in a given project, running your test suite through bash, for instance, without turning off the prompt for genuinely different kinds of commands you have not vetted the same way.

See Configuration for the full settings picture this fits into, and how it interacts with the code theme and effort level settings that are also saved per machine.

A reasonable pattern is starting a new kind of project with everything unapproved by default, watching a few real prompts go by to see whether they look like what you expected, and only then turning on auto-approve for the specific tool, usually bash for a trusted test command, once you have actually seen the pattern hold.

/config run with no argument shows exactly which tools currently have auto-approve turned on, described further in Checking your current settings, so this is never a setting you have to remember by memory alone.