How auto-approve is scoped

Auto-approve is scoped per tool, applied globally on that machine rather than needing to be re-declared per project or per session. Turning it on for bash applies the next time tCode starts, in any folder, on that same account.

If you want a tool auto-approved in one project specifically but not another, the practical approach is turning it on before starting work there and off again afterward with the same command, rather than expecting it to scope itself automatically by folder, since it does not.

This tradeoff, simplicity over automatic per-folder scoping, keeps the mental model of what is currently auto-approved a single, checkable state rather than something that could silently differ folder to folder without you noticing.

It is worth being deliberate about turning a tool's auto-approve back off once you leave a project where you had a specific reason to trust it, rather than leaving it set indefinitely simply because you forgot it was on.

/config is the fast way to check the current state of every auto-approved tool at once before starting work in an unfamiliar project on a machine you have used before, described in Checking your current settings.