Context Actions
Right-clicking a node
The menu is built from what the node actually is, in a fixed order: an "Open" action first — the same drill-in behavior described in Navigating — followed by whatever applies to this specific node:
- Open — always first.
- Rename — workspace nodes only.
- Session lifecycle — Resume or Pause, Restart, and Reveal Home, then Kill, for any node with a live session behind it (a session node, or an agent node with one running).
- Simulate Synapse Flow — agent and session nodes only. See below.
- Start Team… — agent nodes only. It opens the same team-creation form as the Room's own toolbar, with this agent pre-selected as a member. An agent's queued work is reached from its pane header badge, or from Pending Mail (n)… on its node in the Room — see Mail & Counters for what that shows.
- A destructive action, worded for what's actually being removed — see the table below. Not every kind has one.
- Save Bit… — always last, on every node regardless of kind.
Destructive actions by kind
| Node kind | Action | Notes |
|---|---|---|
| Bit (captured note) | Delete Bit | |
| Bit page (session) | Remove Bit Page | |
| File | Remove File | |
| Agent | Delete Agent | |
| Workspace | Delete Workspace | Only offered when more than one workspace exists |
| Memory | Delete Memory | |
| Session | — | Terminated via Kill in the session-lifecycle group above, not a separate destructive entry |
| Task, Decision, Handoff, Artifact, Conflict | — | Read-only projections of the knowledge fabric; nothing here originates from the map |
Right-clicking empty canvas
A separate menu, for creating rather than acting on something that already exists: New Shell Agent, New Bit Page, New File, then, after a divider, New Agent and New Workspace. Each creates its target in the active workspace and selects it immediately.
Simulate Synapse Flow is a visualization only
Both the per-node Simulate Synapse Flow action and the toolbar's Preview Synapse Flow button (see Navigating) do the same kind of thing: they animate a cascade of pulses travelling outward along real connections, starting from a real node. Nothing about running one reads live agent state beyond the graph's existing structure, and nothing about running one triggers, messages, or otherwise acts on any agent. It is a demonstration of how activity would propagate through the shape of your current graph — never a stand-in for, or a trigger of, real agent activity. Treat anything you see ripple across the map during a simulation as exactly that: a simulation.
Where to go next
- Navigating — the toolbar controls these actions duplicate or complement.
- Inspecting Nodes — the same actions, reachable from the inspector instead of a right-click.
- Agent Mesh: Teams & Channels — what Start Team actually creates.