Agents panel

The Agents panel is the narrow panel on the right edge of your primary display. It brings together named agents and coding chats, while keeping each conversation in its proper place. Nock’s own chats are in the separate Chats panel.

Open the panel

Move the pointer to the thin line at the middle of the right screen edge, or click it. Use the lock control to keep the panel open. If the edge line is hidden, check Settings → General → Hide side notch. The panel stays on the primary display.

The panel has two kinds of rows:

• Agents such as agents you made, workers, or connected bots. Selecting a voice-capable agent makes it the recipient for your next Nock talk hold. The recipient is fixed when the hold starts; changing rows during a recording does not redirect it.
• Coding chats from Claude Code, Codex, OpenCode, or local Grok Build, including tasks Nock started with Claude Code or Codex. Selecting one opens that conversation in its own chat window, not in Nock’s notch. To speak to these chats, use Chat Manager; typing in the chat window is another option.

Read status and open the right chat

Coding chats are grouped by project, with worktree details on each chat. The main list follows your latest working day, measured from your newest chat activity rather than today’s date. A week away does not empty it. Chats open anywhere, working, or waiting on you stay visible even when older.

Older chats at the bottom contains earlier closed chats, newest first. Expand it to reopen a conversation; search looks through the full history without requiring that fold to be open. Older closed chats are not counted as running agents. A + beside a project starts a new coding chat there; use the project menu when you want a separate worktree. New chat starts a conversation in the selected tool and folder. New Grok chat is offered when local Grok Build is installed; it is not the separate Grok Bot integration.

Status labels help you choose what to open:

• Needs you means the chat is waiting for your answer.
• A spinning ring or Working… means it is active.
• New result means a result is ready for you to read.
• A grey or idle state means no current activity is reported.

Open the row to read the conversation and any question. A state dot is a summary, not proof that the requested work or its tests succeeded. See Chat windows and Inbox for the full history and attention cards.

The top Chat Manager row opens the second agent that organizes your coding chats. Click it to use its picker and conversation; hold Option + Command on Mac or Ctrl + Alt + Win on Windows to talk to it. Those are separate from Nock’s own talk shortcut. See Chat Manager.

Agents, questions, and return to Nock

Click an agent’s orb to open its thread. If it can take voice, the notch shows which agent is selected. Back to Nock, pressing Escape, or toggling that agent returns the voice target to Nock. A coding chat is never made the voice target just by opening its row; use Chat Manager to address it.

When an agent asks you a question, read it before choosing an answer. Depending on the row, you can select a choice or Type your own answer, then press Submit. Coding chat questions have their own answer controls in the chat window or Chat Manager. See Chat Manager commands.

Use the row’s menu to rename or close a chat where those actions are available. Closing a chat is not the same as stopping a task. Deleting or closing a row can stop active work; read the confirmation and see Background tasks before proceeding.

Notifications

Open the coding-chat Inbox from Chat Manager or the inbox button on top of the slim right-edge notification pill. The Agents bar header does not contain an Inbox button. These cards are separate from Team & inbox, which holds messages from people and connected agents. See Coding-chat Inbox and Team messaging.

While the Agents bar is closed, the edge pill can alert you when a found chat finishes, needs an answer, fails, or has new output. A minimized title bar or corner bubble still counts as out of view; a full chat window in front of you does not. A held talk key defers the pop-up until you release it. Click the chat’s circle to open it and mark that change seen. The Agents tab’s count covers unseen results or questions, not every saved chat.

Turn off Settings → Agent → Find agents → Edge pop-ups if you want the pill quiet. The panel’s count remains. A notification summarizes a change; it is not proof that the task succeeded.

For how Nock discovers chats you already have open, see Find coding chats. For a chat opened in Nock, your terminal, or the Codex app, see Chat windows.

Choose what Nock finds

Open Settings → Agent → Find agents to control discovery. The main Find agents switch is on by default. When it is off, Nock stops reading coding-tool session lists and the panel shows only Nock’s own agents. Under Show agents from, independently control Show Claude Code agents, Show Codex agents, Show OpenCode agents, and Show Grok agents. The Grok switch reads local Grok Build’s saved chats and active sessions, not Grok Bot. A tool that is not installed shows no chats.

In the Advanced section, Add found agents can be Automatically (the default) or Ask me before adding a newly found chat to the panel. Group by can be Project or Tool. Edge pop-ups controls the small notification pill shown when the panel is closed; turning it off does not hide the Agents panel’s count. Live status from Claude Code, Codex and OpenCode is off by default; enabling it adds optional status hooks so state changes can arrive sooner. Without those hooks, discovery and status reading still work.

Grok Build has no optional status hook. Nock uses its own session records and live output for the state it can report. Discovery reads the tools’ own session lists; it does not transfer their sign-ins or turn every historical chat into an active agent.

The Open an agent’s chat in choice applies to Nock’s own named agents: choose The notch or The chat pane. Found coding chats always open in their own chat window. This setting does not make the coding chat a voice recipient; use Chat Manager to talk to a coding chat. See Coding task troubleshooting if a chat is missing.