/communicate
How agents and threads message each other — the inbox mechanics, which submission surface YOUR context actually has, steering a running round, and finding "the thread which does XYZ" as ordinary mesh data.
- Instructions: You are communicating **between agents and threads**. On this platform there is exactly one messaging medium: the **Thread**. Agents, users, and external clients message each other by submitting into a thread's inbox — there is no separate DM system, no bespoke message request types, and you must never invent one. # 1. The medium — a thread's inbox Every conversation is a `Thread` node at `{owner}/_Thread/{id}`. Its `content.pendingUserMessages` is the **inbox**: submitted-but-not-yet-ingested messages. Two things drain it, and only these two: - **At rest** (`status: Idle`/`Cancelled`): the submission watcher picks the messages up and dispatches a new round. - **Mid-round** (`status: StartingExecution`/`Executing`): the executing agent's `check_inbox` tool drains them between steps — the message is delivered inline into the live response (Claude-Code style). This is how a running thread is STEERED: a submission reaches it without waiting for the round to finish. 🚨 **Never edit `pendingUserMessages`, `messages`, or the id bookkeeping by hand.** They are owned by the submission watcher; a hand-written entry is not ingested the way a real submission is, and a half-written pair leaves the thread stuck (see `/thread`). # 2. Sending — know which surface YOU are on Submission belongs to the thread API, and which piece of it you have depends on where you run: - **You are an agent executing IN a thread** (the composer dispatched you): your reach is your own conversation plus the sub-threads you dispatched. `delegate_to_agent(agentName, task, context?)` opens a sub-thread (the delegate sees your `task` text and the `context` path, nothing else — write the task self-contained); `send_to_sub_thread(path, message)` steers a running delegate; `list_sub_threads()` shows what you dispatched. 🚨 **There is no "message any thread" tool on this surface.** A thread you did not dispatch is not addressable from here — the way to reach another conversation is t…
- Auto mount: yes
- Launches sub thread: no