How Nock coordinates chats and agents
Choose the right place for your request: Nock, Chat Manager, a coding task, a worker, or Team.
Nock has several kinds of agent conversations. The names may sound similar, but each has a different job and a different place to review it.
| If you want to… | Use… | You follow it in… |
|---|---|---|
| Ask a question, make a reminder, use an app, or ask Nock to do something | Nock, the main voice agent | The notch and Nock’s left-side Chats history |
| Ask Nock to build or change a project | A Nock worker or background task | Tasks and the task’s result |
| Ask Claude Code or Codex to carry out a coding task | A coding-agent task | Tasks, or a coding chat when it opens in the agent helper |
| Find, message, or answer an existing Claude Code, Codex, or OpenCode chat | Chat Manager | Chat Manager, coding-chat Inbox, and the chat’s own window |
| Talk to an agent you created or connected | Select that agent | Its thread on the notch or its own view |
| Hand work to a teammate or outside agent | Team | Team Messages and the shared chat you choose |
| Run a bot on a cloud computer | A cloud bot | Its cloud-agent view and task status; cloud bots are marked Beta |
Nock and Chat Manager are separate agents
Section titled “Nock and Chat Manager are separate agents”Nock’s main voice shortcut—Control + Option by default on Mac—talks to Nock. Nock handles ordinary requests, can use its tools, and may start workers or coding tasks. Its conversation history is in the left-side Chats panel.
Chat Manager has its own shortcut: Option + Command on Mac and Ctrl + Alt + Win on Windows. It manages coding chats you run yourself. It can find the chat, open it in a separate window, pass your words through, or answer a question when you tell it the choice. It does not take over Nock’s general assistant role or write code itself. See Chat Manager.
A coding task is not the same as a coding chat
Section titled “A coding task is not the same as a coding chat”When Nock starts a task for Claude Code or Codex, the work is tracked as a task. With Find agents enabled, an eligible task may open as a chat in the agent helper. Either way, open the task or chat to see its progress and questions. Existing coding chats appear under project groups in the Agents panel, and each opens in its own chat window.
Use Stop task to interrupt a background task. A Chat Manager “stop” command stops the current step but keeps the chat open; “close” closes it. A voice follow-up does not necessarily stop a running task.
Team is a handoff path, not another local worker
Section titled “Team is a handoff path, not another local worker”Team messages connect people, your other computers, shared chats, and outside agents. A message can be queued or delivered without being answered. Team messages wait in the Team inbox by default; sharing a chat or enabling the per-chat automatic-delivery option is a separate action. Team does not replace Nock’s task controls or a coding chat’s permission prompts. See Team and Shared chats.
Keep attention surfaces distinct
Section titled “Keep attention surfaces distinct”- Nock Chats: saved conversations with Nock.
- Tasks: background work Nock or a coding tool is doing.
- Agents panel: named agents and coding chats, grouped by project.
- Coding-chat Inbox: completed results, questions, errors, and missed messages.
- Team Messages: peer handoffs and outside-agent inbox messages.
If the question is “what is still working?”, open Tasks. If it is “which coding chat needs me?”, open Chat Manager or the coding-chat Inbox. If it is “what did my teammate send?”, open Team Messages.