Auto mode

Auto mode lets an interactive agent approve its own routine actions, so you aren't asked about every test run or file edit. Anything that isn't routine still comes to you as a permission request.

Switch modes

In the agent's terminal, press Shift+Tab to cycle the agent's mode. The current mode is shown at the bottom left.

Mode What the agent does
Build Works on the task and asks before any action outside its permissions.
Plan Reads and plans without changing files.
Auto Works like Build, but approves routine actions itself and asks about everything else.

Auto is offered only when the agent asks before unlisted actions (Ask me, which codity agent uses by default). An agent set to Refuse never asks, so there is nothing for Auto to approve and it isn't offered.

What Auto approves

Action Approved when
Reading, searching, listing and editing files The file is inside the project folder: the Git repository, or, outside a repository, the folder you started the agent in.
Running tests pytest, python -m pytest, python -m unittest, npm test (and the pnpm, yarn and bun equivalents), vitest, jest, go test, cargo test.
Building, type checking and linting npm run build, npm run lint, npm run check, npm run typecheck and their :suffix variants, tsc, eslint, ruff check, ruff format, mypy, flake8, go build, go vet, cargo build, cargo check, cargo clippy, make test, make check, make lint, make build.
Reading the repository git status, git diff, git log, git show, git blame, git ls-files, git rev-parse.
Read-only shell commands ls, cat, head, tail, wc, grep, rg, sort, uniq, cut, diff, stat, echo, pwd, which.

Each command is approved only with common, harmless options, for example pytest -q -k name, go test -run TestParse -count=1 ./... or git log --oneline -5. Any other option gets a permission request. That includes an option that writes a file, such as -o or --output, and one that runs another program, such as --pre, -exec or -toolexec.

What still asks

  • Any command not listed above, such as git push, git commit, npm install, rm or curl.
  • Commands combined with ;, && or |, or that redirect into a file, use $VARIABLES, command substitution or unquoted wildcards (*, ?, [...]).
  • Any file or argument outside the project folder, including absolute paths, ~ and ...
  • .env files (.env.example excepted) and anything under .git, even inside the project, including forms such as git show HEAD:.env.
  • Searches that would read every file in a folder: recursive grep (-r, -R), recursive diff, and rg told to include hidden files (--hidden, -u). Plain rg is approved because it skips hidden files such as .env.
  • Fetching URLs, starting sub-agents and publishing a pull request.

Auto only answers requests that would otherwise come to you. It never overrides a deny rule: actions your agent's permissions or your organization's and team's policies deny are still refused.

See what Auto approved

Every approval appears in the agent's transcript on the dashboard as a notice, for example Auto mode approved bash: python -m pytest -q. Approvals last for that one action. Auto never grants an action for the rest of the run, and never adds a permanent rule.

Turn Auto mode off for your organization or a team

Administrators can remove Auto from the mode cycle by adding auto_approve: false to the organization or a team's agent policy (see Permissions and YAML policies):

version: 1
auto_approve: false
permissions: []

If any policy that applies to an agent sets auto_approve: false, Auto mode is off for that agent. Leaving the field out, or setting it to true, keeps Auto available. Like other policy changes, this takes effect on the agent's next run or resume.

Auto mode decides which of the agent's own requests it answers. It does not isolate the machine. A test run executes your project's code, and the agent can edit that code in Auto mode. Use a restricted machine or container when you need that boundary.