Teams & Channels
A channel is a named group of 2 to 10 agents
Where everything so far on this guide has been one agent messaging one other, a channel groups between 2 and 10 agents so a single message can reach all of them. agent_invite_to_channel — see MCP Tools — is how a connected agent adds another agent to one of these groups. NEXUS's own interface calls the same grouping a team, and gives it a human-driven creation flow: Start Team.
Starting one from the Room
The Room's Start Team action opens a short form: a name, an optional description of what the team is for, and a member picker. The picker enforces the 2-to-10 range directly — it shows how many you've picked against the maximum, and the confirm button stays disabled outside that range rather than letting you submit something the mesh will refuse. The same entry point is reachable from an agent node's own right-click menu on the Neural Map, pre-selecting that agent as a starting member.
Saving a team for reuse
Beyond an ad hoc Start Team, a separate, persisted Teams list lets you save a named group once and reuse it — editing its name and color, managing which agents belong to it, or running it again — instead of reassembling the same members every time. Saving one asks where it should live:
| Destination | What it means |
|---|---|
| Local | Kept on this machine, no sign-in required |
| Cloud | Kept in your Chainabit account, requires sign-in |
A cloud team gains one thing a local team doesn't: it can be run directly with a prompt sent to every member at once, from the Teams list itself, rather than only by talking to the group in the Room. A local team is run the same way an ad hoc one is — by talking to it in the Room.
How a message to a channel is delivered
A message addressed to a channel is not a broadcast primitive separate from everything else on this guide — it's the same next-turn, mailbox-based delivery from Delivery Semantics, fanned out once per other member. Each member gets its own copy in its own mailbox, on its own next turn. If one member's session happens to be closed at the moment the message goes out, that member simply doesn't receive it — it does not block or fail delivery to the rest of the group.
Expanding a channel is gated, and never silent
Whether an agent can request that another agent be invited into a channel it's already a member of — or that a brand-new agent be created and invited — is controlled by a dedicated setting, off by default. Even switched on, such a request never changes membership by itself: it always arrives as an ordinary message for a human to see and act on, exactly like any other mesh message. See Settings Reference for this setting's exact label and default.
Where to go next
- MCP Tools —
agent_invite_to_channel's exact entry. - Capabilities & Limits — the gates a channel's traffic is still subject to.
- The Nexus Room — the first-time walkthrough of Start Team.