Skip to main content
The Ghost Graph is your visual org chart — a live canvas showing which agents are on a team, who routes work to whom, and what each agent is doing right now. Every node and edge maps to real state: a Boo is a real agent record, a dependency edge is a routing rule in that agent’s AGENTS.md, and a skill orbital is a capability from the unified inventory. Nothing on the canvas is decorative. Clawboo renders the graph in two scopes: Atlas (the global all-teams view, opened from the globe icon in the primary nav) and the per-team Ghost Graph (embedded in the top half of each team’s group chat). Both use the same canvas component — what differs is which agents they show and a few Atlas-only controls.

Atlas vs the per-team Ghost Graph

AspectAtlas (globe icon, primary nav)Per-team Ghost Graph (embedded in group chat)
Agents shownEvery agent across all teamsOnly agents in the selected team
Boo ZeroSynthesized at the top, with edges to each team’s internal leaderSynthesized as the team’s apex node
Team halos toggleVisible (Atlas-only)Hidden
Layout pill (Tree / Radial)Visible (Atlas-only)Not applicable
Activity dockSlide-in all-teams live terminalNot present (group chat already narrates the team)
Toolbar chromeFull Atlas toolbarSuppressed — team chat header owns identity
Switching between Atlas and team chat preserves each scope’s saved drag positions independently — they never overwrite each other.

Boo nodes

Each agent appears as a node on the canvas. Nodes have two shapes and morph between them:
  • Idle circle — when the agent isn’t running. Size grows with the number of connections. Shows the agent’s avatar, name, status dot, and a “seen Xm ago” timestamp.
  • Active card (280 × 170) — when the agent is currently running. The card shows a header band (avatar + name + status pill), a live activity feed in the middle (streaming text, recent message, or most recent tool call), and a footer band. The card morphs in when the agent starts working, turning the canvas into a live control room.
Status drives the glow: a running Boo pulses mint, an agent in error glows orange, and a sleeping Boo dims. Hover any node to highlight its connections and dim everything else — the fast way to read one agent’s relationships in a dense graph.

Steps

Expand a Boo’s skills (peacock expand)

Skills and resource orbitals are hidden by default to keep the view focused on team topology.
1

Single-click the Boo

Its skill orbitals fan out with a staggered peacock-feather animation. The canvas re-fits to frame the expanded Boo and its orbitals.
2

Explore the orbitals

Skill nodes appear as mint circles; resource nodes appear as amber cards. Hover a skill node to see an Install → button.
3

Collapse

Single-click the Boo again to collapse its orbitals.
Multiple Boos can be expanded at once — each toggles independently.

Install a skill onto a Boo

Two ways to install a skill from the canvas:
  • Hover a skill node → click Install → → pick a target agent from the dropdown.
  • Drag a skill node directly onto a Boo node.
Both paths route through the same capability pipeline. A toast confirms Installed "<skill>" on <agent>.

Draw a routing edge (connect mode)

Routing edges represent delegation rules — “this agent routes work to that agent.” Adding one from the canvas writes to the source agent’s AGENTS.md.
1

Enter connect mode

Click Connect in the top-right toolbar. The button reads Drawing Edges while active, and connection handles appear on every Boo.
2

Draw the edge

Drag from one Boo to another. Clawboo optimistically adds the edge on the canvas and appends a routing rule to the source agent’s AGENTS.md.
3

Confirm

A success toast confirms the write. If the write fails, the optimistic edge rolls back with an error toast.
Drawing the same edge twice is a no-op — you’ll get a <target> already in routing toast and nothing is written.

Remove a routing edge

1

Click the edge

An edge explain panel appears at the bottom center, naming the connection, the source agent, and the backing file.
2

Click Remove Connection

The edge is removed optimistically and the source agent’s AGENTS.md is updated. On failure the edge is restored.

Right-click a Boo

Right-clicking any Boo opens its context menu:
ActionWhat it does
ChatOpens this Boo’s 1:1 agent detail view
Edit personalityOpens the agent detail view on the personality sliders
Edit filesOpens the agent detail view on the file editor
Select in sidebarHighlights the agent in the fleet sidebar without leaving the graph
DeletePermanently deletes the agent — no undo

Re-layout

Click Re-layout in the top-right toolbar to recompute all positions from scratch. Use it after adding agents or routes if the auto-layout looks tangled. The fresh positions are saved, so a page refresh won’t re-scramble the graph.

Atlas-only controls

Tree vs Radial layout

A segmented pill in the Atlas toolbar toggles the global topology:
  • Tree — Boo Zero at the top, teams in a flat row beneath it.
  • Radial (default) — Boo Zero at the center, teams arranged as petals around it.
Each mode keeps its own saved drag positions — flipping layouts never drags one mode’s coordinates into the other. Your choice persists across reloads.

Team halos

Click Team halos (pin icon) to draw a colored convex-hull background behind each team’s Boos. Single-agent teams render no halo. The toggle is off by default.

Activity dock

Click Activity (terminal icon) to slide in a right-edge live-activity feed scoped to all teams — the “what is every team doing right now” view.

The MiniMap

The MiniMap overview (bottom-right) is hidden by default. Click the map icon at the bottom-right to show it. Collapsed skill and resource orbitals appear transparent in the MiniMap — so at rest, only Boo dots are visible. Expanding a Boo’s skills makes their dots appear in the MiniMap in sync.

Troubleshooting

Boos pile up at the top-left after switching Atlas layouts. Stale saved positions from one layout mode can bleed into another. Click Re-layout to force a fresh ELK pass — it drops stale positions and persists clean ones.
Connect mode does nothing when you drag between Boos. Drawing a routing edge writes through the connected runtime. If no runtime is connected, the write is skipped silently. Confirm the runtime is connected and the fleet is hydrated, then try again.
  • Agents — edit SOUL / IDENTITY / TOOLS / AGENTS files and personality sliders
  • Group Chat — the team chat where the per-team Ghost Graph is embedded
  • Approvals — pending approvals show as an amber ring on the relevant Boo node
  • Marketplace — deploy agents and teams that appear on the graph