Settings overview
Every Preferences page, how settings are saved, and how projects override them.
Open Preferences with ⌘, or /settings. Search all settings finds any row. Each row has a reset link that returns it to its default. Reset to Defaults resets every setting on the screen. Projects, providers and directories stay. Open config file opens ~/.config/kc/config.toml, where KodaCode saves every setting. When you change a row marked Restarts containers, KodaCode restarts the running project containers.
Pages
| Group | Page | What it covers |
|---|---|---|
| Agent | General | Limits per turn, provider errors, storage, close behaviour |
| Agent | Background work | Parallel autonomous tasks, the default goal budget, reminders |
| Agent | Permissions & sandbox | Where commands run, file access, approvals, secrets |
| Features | Code review | Review agents, challenging findings, scanners |
| Features | Search | Web search and Exa |
| Features | MCP servers | Add, approve and sign in to servers |
| Features | Hooks | Approve and disable hooks |
| Features | Memory | Use memory |
| Features | Crew Workflow | Crew models, limits, retries, skills and memory |
| Look | Appearance | Theme, text, transcript, motion |
| Models & agents | Models & providers, Agents | Separate screens |
Projects override defaults
The Runs on chip beside the prompt box gives each saved project its own settings:
- Sandbox.
- Base image.
- Approvals.
- Review after every turn.
- Parallel autonomous tasks.
A project's own choice wins over the defaults here. See Projects.
Each settings page below lists its rows word for word as the app shows them. Their defaults and config.toml keys follow.