Coding agents

Nock can do coding work itself, start a Claude Code or Codex task for you, or help you manage coding chats you opened in Claude Code, Codex, OpenCode, or local Grok Build. These are different routes. Choose the one that matches how you want to work.

What you want	Use	Where you follow it
Ask Nock to build or change something	Hold Nock’s talk keys and describe the outcome	The task card, Tasks, or its worker chat
Ask Claude Code or Codex to do a task	Name the coding agent and project in your request	Tasks or a chat in the Agents panel
Manage chats you started in a coding tool	Use Chat Manager	Chat Manager, Inbox, and each chat’s own window
Hand work to a teammate or an outside agent	Use Team	Team messages and the shared chat you selected

See Chat Manager, Agents panel, and Team for those separate workflows.

Ask Nock to do coding work

Hold Nock’s talk shortcut—Control + Option by default on Mac—and say what you want built or changed. Give it a concrete result and name the project when you mean an existing one. For example:

In the billing service, fix the test that fails when a coupon expires. Run that test and tell me what changed.

Nock can inspect a project, edit files, run commands, and use available code search or language tools. Work that takes time runs in the background so you can keep talking to Nock. Open the task to see progress, questions, and the result. A completed status means the run ended; still inspect the diff and test output before relying on the change.

For project selection and folder access, see Project folders. For how to track work, see Background tasks.

Start a Claude Code or Codex task

Name the tool so Nock routes the work to the coding agent you intend. Include the project and whether you want a review or edits:

Have Codex review the checkout tests in my shop project without changing files.

Or:

Ask Claude Code to update the sign-in form in my storefront, then run its focused test.

Nock looks up the project you named and shows which project it selected. If several folders could match, name the folder more specifically. Nock will not use a whole home folder or disk root as a project. A folder outside Nock Projects may ask once for access.

On Settings → Agent → Find agents, Nock can open a Claude Code or Codex task as a chat in its agent helper. You can read the conversation, its actions, and its questions in the chat window. A follow-up continues that same session; it does not start a duplicate task. If this route is not available for a particular request, Nock reports that it started the task in the background instead. Chained work, read-only requests, Grok Bot, and cloud bots use task cards rather than a coding chat window.

Coding agents use their own sign-in and provider limits. A subscription may cover a run if the provider and account make it eligible; check the coding tool’s account and billing settings if unsure. See Coding permissions for how Nock passes through your permission choice.

Use local Grok Build chats

With Grok Build installed, enable Settings → Agent → Find agents → Show Grok agents. Nock reads its saved chats and active sessions on this computer. Open an existing chat from the Agents panel, or use New Grok chat where offered to start one in a project. Your next message to a closed chat resumes that same conversation through the agent helper.

If the chat is already running in another terminal, Nock does not start a second copy behind your back; open it there or confirm moving it into the helper. Grok does not use the optional Claude Code/Codex/OpenCode status hooks. Its own session records and live output supply the available state. Grok Build is not the external Grok Bot connection and is not NockBot.

Choose where a build runs

Open Settings → Agent → Build with to choose the default destination for new builds. Depending on setup and plan, the choices include V3Code workers, Claude Code, Codex, or a connected Grok Bot. Each option shows whether it is ready on this computer. If you have not chosen one, Nock selects an available route and labels it Picked for you. Naming a tool in a request—for example, “have Codex do it”—overrides the default for that request. A task already open in a coding chat does not silently change this preference; use a follow-up in that chat or start a new agent request. See Project folders and Coding permissions.

For Claude Code or Codex tasks, use the model pill on a task card to choose Model & effort. It is not a Settings control. The selected model and effort are remembered for that tool’s next task or follow-up; a connected Grok Bot chooses its model in its own settings. See Chat windows.

Follow up, stop, or continue

Open the task card or its chat before sending more instructions. A follow-up to a busy task may queue until the current response finishes; it does not necessarily interrupt the task. Use Stop task to stop a background coding task. A stopped or failed task may be continued from Tasks; inspect its existing changes before asking it to try again. See Continue a task.

Review the outcome

Read the answer, inspect the files changed, and check the tests the task actually ran. If a test failed, distinguish that from a task that merely completed. For a task with a question, answer the question in its own chat or through Chat Manager; ordinary Nock approval cards and coding-agent prompts are not the same system.

For help with a task that will not start or is waiting, see Coding task troubleshooting. For Nock’s general action cards, see Task approvals.