Coding permissions

Open Settings → Agent → Coding agent permissions to choose how a supported coding agent handles work launched through Nock. The current candidate offers Auto, Ask me, and Full access.

Mode	What to expect
Auto	The integration uses the coding agent’s own reviewer and supported restrictions; escalated requests come to you.
Ask me	A more interactive approval mode. Exact prompts depend on the coding agent and action.
Full access	Removes major approval and sandbox protections. The agent can run commands and change files with broad access.

Start with a constrained mode and a specific project. Do not choose Full access simply to make a failing or blocked task continue. Read the requested action and its consequences first.

When a change takes effect

The setting applies to a coding run Nock next starts or resumes. It does not retroactively undo a command that already ran. Read-only work remains read-only in the intended integration path, but verify the task’s scope and results rather than relying on a label alone.

Questions are not permissions

The separate Answer for me after 2 minutes control can answer eligible clarification questions. It is not a blanket approval for risky operations and does not answer permission prompts. If a task needs your authorization, review the card yourself.

For a permission request, inspect the action, project, and scope of any persistent approval. Allow once and session-wide choices are not equivalent. Decline when the request exceeds the task you intended.

Recover from a blocked task

Read the prompt or error, decide whether the action belongs in scope, and answer explicitly. If it does not, stop the task and give a narrower request. After any unexpected modification, inspect the diff before starting another run; do not discard unrelated local changes.

Continue with Coding agents and Troubleshooting.