Coding task troubleshooting

Start by reading the task or chat’s exact status. Queued, Needs you, Stopped, and Failed point to different next steps. Before retrying, check whether the first attempt made changes or completed the action.

The tool or chat does not start

Name the tool and project explicitly: “Have Codex review the tests in my storefront without changing files.” Confirm the project path shown on the card is the checkout you intend to use. If the folder is ambiguous, name it more precisely; see Project folders.

Claude Code, Codex, and OpenCode must be installed and signed in using their own supported setup. If Nock cannot find a coding tool, first check that it launches from your normal terminal, then reopen Nock and try again. Resolve sign-in, subscription, and credit messages in that provider’s own app or account; do not paste credentials into a Nock prompt.

With Find agents on, an eligible Claude Code or Codex request can open in the agent helper as a chat. Other work—including chained requests and read-only tasks—uses a background task card. Check Coding agents before assuming one route is broken.

If a build does not begin, check Settings → Agent → Build with: a selected destination must be set up on this computer. Use Check again after installing or signing in to a tool. If the selected tool is unavailable, Nock reports that instead of silently switching to another provider. See Coding agents.

A chat is missing or will not open

Check Settings → Agent → Find agents and confirm that the tool you use is enabled. Open the Agents panel and check the project’s Saved group as well as its open chats. Nock reads coding-chat history only for tools you have enabled; a removed or unavailable transcript cannot be restored from a row alone.

If a chat is open in your terminal, Nock does not type into that terminal. Chat Manager may offer Move it here and send; confirm the move only if you want the same chat to continue in Nock’s agent helper. A chat in the Codex app stays in that app—use Open in Codex. See Chat windows.

If a chat shows “Opening…” but never opens, use its visible error, refresh the Agents list, and try again once. Do not create a replacement chat until you have checked the original session.

It is queued or waiting for you

Queued means the task has not started yet. It may be waiting for another task in the same project or for a task it was chained behind. Open the card and inspect the dependency before sending a duplicate.

Needs you or Waiting for you means the coding tool has asked a question or permission prompt. Read the question in that chat window and choose the intended option. Chat Manager can pass through your explicit answer to supported questions. Answer for me after 2 minutes only applies to eligible background coding-task questions; it never answers permission prompts or questions in an agent-helper chat, and it does not act on Team requests. See Coding permissions and Inbox.

Code search or checking is unavailable

In Settings → Agent → Code index, Index: no project folder yet means Nock has not indexed a project in this engine session; name a project or start a coding task there. Index: building is still in progress. If the status says code model missing, text search only, plain text search still works. Use Rebuild after an error. For language-server status, open Settings → Agent → Coding tools; if a supported optional server is not ready, review Download language servers when needed and the status reason. See Code search and language tools.

The run stopped, failed, or will not respond

Open the task and read its final line. Check the project’s diff before asking again; partial edits may remain. Use Stop task if the task is still running and you want it interrupted. A voice follow-up does not necessarily stop a run.

For a task that can continue, choose Continue on its card or tell Nock which task to continue. It resumes in the same project where supported; it does not guarantee the old session is still available. See Continue a task.

If a provider reports a usage or connection error, verify it with that provider. For an OpenCode chat, confirm its own process is responding. Do not infer that the coding task succeeded just because Nock or the helper is still open.

Report a problem

Include the Nock version, tool name, task status, project name (not private source or credential contents), and sanitized error text. Remove tokens, account identifiers, and private code before sharing. See Support.