Permissions and approvals
Cocode is designed to keep work moving while making consequential actions inspectable, rejectable, and recoverable. Controls are gated by runtime capabilities; unsupported actions remain unavailable.
Permission modes
manual: approve sensitive actions individually.auto-edit: allow edit actions while retaining approval for other high-risk actions.plan: plan and inspect without performing writes.auto: shown only when the runtime declares support.
In TUI, Shift+Tab changes permission mode and Ctrl+M changes input mode. GUI follows its current in-app controls.
Actions that commonly require approval
- Writing, deleting, or batch-editing files.
- Commands that can change the environment.
- External network or third-party service access.
- Connectors that require additional credentials.
The approval panel supports allow once (Enter / a), allow for this turn (t), deny (d / n), and cancel. Timeouts, disconnects, duplicate responses, and capability mismatches fail closed.
Before approving, check that the action belongs to the task, the scope is bounded, a smaller check is not better, and the result has a verification path. API keys, OAuth tokens, and provider secrets must not be written to session logs; share only redacted diagnostics when reporting issues.