Shared chats and Team handoffs

Shared chats lets teammates and connected outside agents address a particular conversation already visible in Nock. It is optional: you can read and reply in Team Inbox without sharing any chat.

Share a selected chat

1. Open Settings → Team → Shared chats.
2. Find the conversation you want to make available and choose Share chat.
3. Leave Allow teammate messages to reach this chat without asking off if you want to review each request first.

Nock needs a stable conversation identity before it can share a chat. If the entry says it is unavailable, open that chat, refresh Team, and read the explanation. Choose Stop sharing to remove its destination from the Team directory.

Sharing exposes directory details such as the title, tool, status, project-folder name, and branch. It does not publish the existing transcript, local files, or workspace contents. It gives others an address to send a new message to—not general access to the conversation or computer.

Review an incoming handoff

Open the conversation in Team & inbox or Settings → Team → Messages. Expand Review message beneath the incoming message.

• Keep in inbox marks it reviewed without sending it into a local coding chat. For mail addressed to an outside agent, this makes it available when that agent checks its own inbox.
• Send to chat passes the message text to the selected local chat. For a message addressed to a shared chat, the original conversation must still be available; Nock does not substitute another chat with a similar name.
• Reject rejects that incoming message rather than forwarding it.

Opening the conversation marks visible messages read locally. That is different from review or delivery. Replying sends your answer to the original sender; it does not release a held request addressed to a shared chat or outside agent.

What reaches the coding chat

Nock labels a forwarded message as teammate input, not as the owner’s approval. Send to chat forwards the message text; it does not grant file access, open an attachment, or approve the coding agent’s tools.

Sent to the selected chat describes the handoff, not the outcome of the work. Open the destination chat to read its reply, check its result, and answer any separate permission question. If delivery is unconfirmed, inspect that chat before trying again so you do not duplicate a request.

Allow automatic delivery for one chat

Turn on Allow teammate messages to reach this chat without asking only for a shared chat you want to receive Team requests automatically. This is a per-chat choice; other shared chats still wait for review. Turn it off or choose Stop sharing to end that behavior.

Automatic delivery does not approve the agent’s own permission prompts or make incoming peer text an instruction from you. A connected agent’s request to run a command still follows the destination agent’s permissions.

Use the right inbox

Team Inbox holds conversations and handoffs with people and connected agents. The coding-chat Inbox holds attention cards for local coding chats that finished, have a question, failed, or missed a message. Reading a Team message does not itself create a coding-chat attention card.