Coding task troubleshooting

Start with the task card’s exact state. A task that is Queued needs a different response from one that is Waiting for you or Couldn’t finish. Read the existing task before dispatching another copy of the same request.

The task never starts

Name the integration explicitly: “Have Codex review this project” or “Ask Claude Code to explain this test failure.” Identify the project folder and whether edits are allowed. Without that distinction, Nock may answer the question in its own conversation.

If the command-line agent cannot be found, open a new system terminal and check that its normal launch command works. Install and sign in through that provider’s supported process. Quit and reopen Nock after installation so its command lookup can refresh. Do not replace Nock’s application files or paste credentials into a task description.

A working command in one old terminal session does not prove that a newly launched desktop app can find it. Include the command name and installation method when reporting a detection problem. Account or credit errors from the coding provider should be resolved in that provider’s own interface.

The folder is missing or ambiguous

Give the full project path when several folders have the same name. Check that the selected path is the current checkout, not a stale copy. Nock deliberately avoids using the entire home directory or disk root as the coding project.

Before allowing edits, preserve existing work and check which other tasks use the folder. A successful run in the wrong checkout will not fix the project you are looking at.

Queued or waiting

Coding tasks are limited by available worker slots and project ownership. Only one task runs in a project folder at a time. A chained task can wait for its predecessor and may not start if that earlier task fails. Inspect that dependency before retrying.

For Waiting for you, open the question or permission request and answer it directly. Automatic answers, when enabled, do not cover every sensitive decision. They are not a substitute for a missing approval. See Coding permissions.

Stopped or interrupted work

The runtime can stop a task after prolonged silence or its overall time limit. Tasks interrupted by quitting Nock are not automatically resumed. Inspect the project diff and task output before starting a follow-up, because partial changes can remain.

Use Stop task to interrupt a running coding task. A voice follow-up can queue behind the existing work instead of stopping it. If you opened the session in the coding provider’s application, continue there and check its state before launching a second session in Nock.

For a support report, include the task state, integration, app version, and sanitized error. Remove secrets and private project contents. Distinguish “process completed” from “tests passed” when describing the result.