Right Rail¶
The right side of the window is a single utility pane with a vertical icon strip you click to switch contents. Eight sections:
| Pane | What's in it |
|---|---|
| Tools | Runtimes, workspace agent CRUD, MCP servers |
| Context | Context-budget telemetry + summarize/compact controls |
| Review | Pending proposals (quorum votes + agreement-gated implement) and queued work: unanswered agent mentions + host status |
| People | Members, presence, roles, invites |
| Vaults | Reference-material sources mounted into the session |
| Skills | Instruction bundles injected into participants' prompts |
| Workflows | Agent pipelines: definitions, live runs, gates — see Agentic workflows |
| Activity | Streaming runtime activity for the workspace |
Switching panes preserves the visible width. Click the × in the
pane header to close the rail entirely.
When to use each¶
- Tools: workspace agents (add/edit/remove), the active runtime, and MCP servers — open it when a run is in flight (it shows each agent's planning → working → awaiting-review state) or when an MCP server is misbehaving and you want to disable a tool. The wrench glyph in the chat header also opens this pane.
- Context: when a chat's reasoning depends on specific facts. Shows the context-budget telemetry and the summarize/compact controls; pinning a context item bumps it to the top of the conversation prompt.
- Review: when an agent has proposed a write. An agent raises a
proposal by ending a reply with a
[[propose: …]]directive; it's saved here for review, never auto-run. Lists pending proposals, lets you claim / approve / disposition — approval counts at the voter's real role and an author can't approve their own — then Implement once quorum is met. See agent-authored proposals. It also shows Queued work — every unanswered@agentmention with its host's live status (online / offline / owner-device). If an agent's host is offline, a Run on worker button reassigns it to an online worker so the backlog drains without waiting for that laptop to wake. See Headless agents. - People: members, online status, invites, cross-network rendezvous status, nearby-on-LAN peers.
Why a single rail¶
The icon strip + tinted card is the only chrome that needs to exist for these signals. A window-level toolbar duplicating the same affordances would just steal screen space; the rail is the canonical place to switch panes and close them.