Choose an execution mode
The mode selector controls how code changes move from request to execution.
Choose the right mode
Pick by how much review the work needs, not by how large it looks:
- Auto
- You want CodeZero to decide whether planning is necessary. Each edit or command is still confirmed.
- Planned
- You want every change planned and approved first.
- Normal
- You want to work directly, with individual confirmations.
- Coffee Mode
- The plan is approved and CodeZero can continue unattended.
Auto Mode
Auto is the default. Small, unambiguous changes can proceed directly, with each edit or command still shown for confirmation. Larger changes move into planning automatically.
Auto keeps a request direct only when the change is tightly scoped, touches a small amount of code, introduces no new configuration or API surface, and does not require a design decision.
Planned Mode
Every change goes through a plan. Source files and commands are blocked until the plan has been reviewed and approved.
Normal Mode
No plan is created automatically. The agent can propose edits and commands, and you confirm each change individually.
Override Auto for one request
In Auto mode, prefix a request with /plan to force planning, or /quick to force a direct change for that message.
Work with Plans and Tasks
After approval, CodeZero breaks the plan into phases and tasks. Tasks can track pending, in-progress, completed and blocked work and can show dependencies between items.
Run an individual task or use Run all to work through the remaining items in order.
When work spans repositories, Tasks shows which repository each part belongs to. It can also surface work from your other CodeZero tabs and, when you choose to show it, work started by other people on your team.