KodaCode
Coming soon
Docs/Working with the agent

Approvals

Choose what asks first and what runs straight through, on your machine and in a container.

Two questions decide whether the agent waits for you:

  • Does the change stay inside the project?
  • Does the project run on this computer or in a container?

The defaults

Set the defaults in Preferences → Permissions & sandbox → Approvals. Set them per project on the Runs on chip. A project's own choice wins.

SettingOn this computerIn a containerOptions
Changes inside the projectAsk before eachApply directlyAsk before each, Apply directly
Commands that reach outside the projectAsk firstAllowAsk first, Allow, Deny
MCP toolsAutoAutoAuto, Writes, Always, Never
  • Changes inside the project covers each file edit and each command that adds, edits, deletes or downloads files.
  • Commands that reach outside the project covers a command that touches paths outside the project, rewrites git history or changes the system. Only the places that a command names decide whether it asks. Allow here applies to your sessions. Autonomous tasks run these commands only when the project itself chooses Allow.
  • MCP tools: Auto asks unless the server marks a tool read-only. Writes asks for anything that is not read-only. Always asks at every call. With Never, it never asks. A server's own approval in MCP servers wins.

The approval card

An Approval required card shows the edit's diff or the command. You can:

  • Approve (↵) or Deny (⌫).
  • Add a Note for the agent. KodaCode sends it with your answer.
  • Allow this tool for the session or Allow this command for the session. KodaCode stops asking for it until the app closes.

You can also accept or reject edits in the editor, which shows the proposed change in place.

Outside the project

KodaCode refuses everything outside the open project unless Additional Directories (Permissions & sandbox → File Access) lists it. A change in a listed directory asks for approval like any other change. KodaCode refuses an entry that is switched off, but keeps it in the list.

Autonomous tasks get automatic approval inside the project. Autonomous tasks outside the project lets them read and write outside it too.

Autonomous work

Goals, automations, background subagents and crews follow the project's settings. When a crew worker's edit needs approval, it waits in the session that started the crew.