# What you can ask Chat Manager Chat Manager looks after coding chats you run in Claude Code, Codex, OpenCode, and local Grok Build. It can find a chat, send it your words, start or reopen a chat, show its status, answer a question when you tell it which choice to make, and run a command in a visible pane. It does not write code itself. For the basic controls and shortcut, see [Chat Manager](/nock/chat-manager). For Nock's own requests and tasks, use its main voice agent instead. ## Message a chat Examples: - “Tell the login chat to add a test.” - “Ask Codex what's left in the shop project.” - “In the billing chat, make the refund path faster.” You can identify a chat by its title, a nickname in Chat Manager's notes, or its project. If several chats match, Chat Manager looks at their title and short summary and asks you to choose if it remains uncertain. It never picks a chat just because that app is in front of you. A chat open in your own terminal must be named explicitly. When a chat is open in your terminal, Chat Manager says it is there and offers to move it into the Nock agent helper. It sends your words only after you confirm. If you say no, the chat does not move and no message is sent. A chat in the Codex app stays there; use **Open in Codex** to continue in that app. Chats open in the Claude app are not in Chat Manager's list. ## Start, reopen, or show a chat - “Start Codex in shop” creates a chat in that project. If you do not name the tool, Chat Manager uses the one you have used most in that project, or Claude Code when there is no recent choice. - “Start a Grok chat in shop” chooses local Grok Build when installed. This is a local coding chat, not a request to the separate Grok Bot integration. - “Add dark mode in a new worktree” creates a separate checkout because you explicitly asked for one. Chat Manager does not create a worktree unless you ask for one, such as “new worktree,” “own branch,” or “separate checkout.” - “Bring back the search chat” reopens the existing chat in its project, with its history. Add the task in the same message if you want to send a follow-up too. - “Show the login chat” opens the matching chat in its own window. Add “in the terminal” to open it in the agent helper's terminal pane when that route is available. Chat Manager does not guess a folder. If the named project is unclear, it asks and shows the real choices. Two chats may use the same project and folder; say which chat you mean when that distinction matters. ## Stop is not close Say **stop**, **hold on**, or **pause it** to stop the current step while keeping the chat and its history. Say **close it**, **quit it**, or **I'm finished with it** to close the chat. A closed chat can be reopened later. Chat Manager checks that your request is a stop or close instruction before acting; it does not stop or close a chat on its own. To rename a chat, say “Rename the login chat to sign-in” or “Call it docs.” A title change is shared with the chat's other Nock windows and lists. ## Answer a chat's question When a coding chat asks a question, tell Chat Manager the specific answer: “yes, allow it,” “the second one,” “three,” “no, skip it,” or the option's own words. It re-reads the question and its options before acting. If the question changed, it presses nothing and tells you. After a valid answer, you have **two seconds** to press **Undo** or Escape. A plain “yes” chooses the matching yes option. If the question offers both “yes” and a broader choice like “yes, and don't ask again,” specify the wider choice or its number. “No” never selects a yes option. A chat question is not the same as a Nock action-approval card or the coding-agent permission mode; see [Task approvals](/nock/task-approvals) and [Coding permissions](/nock/coding-permissions). ## Run a command You can ask Chat Manager to run a command in a new visible pane—for example, “Run the tests beside the login chat” or “git status in shop.” Commands that could delete or overwrite files, reset work, force-push, remove a checkout, sign in, need admin rights, stop programs, access keys, change the agent helper, or edit shell startup settings are refused. If it refuses, review the reason and run the command yourself in your terminal if appropriate. The command guard does not make every allowed command risk-free. Keep commands specific to the project, read the command Chat Manager is about to run, and inspect the result. ## Use the screen only when you refer to it When you ask “what is this error?” or “what's on this page?”, Chat Manager can use the front window context. On Mac, asking about a browser page may require a one-time permission to read its address. On Windows it uses the window title. A screen picture is used only when your words ask about something on screen; game mode suppresses screen context. The chat information Chat Manager uses for routing includes titles, short summaries, recent lines, project names, and its notes. See [Memory and context](/nock/memory) and [Privacy](/nock/privacy).