Files
nntrivi2001 57dc91585d feat: Claude Code Monitor — lanes, pipelines and a merged workspace
Internal SmartGift build of a Claude Code monitoring dashboard.

Lanes: a durable unit of parallel agent work, one per working directory,
tracked across session restarts. Managed lanes are git worktrees the
dashboard provisions and can reset or remove behind a three-check destroy
guard and a counted preflight; adopted lanes are directories you already
own and are never destroyable.

Pipelines: a lane moves through pipeline stages. A stage the agent declares
with evidence renders green; a stage inferred from the tool-event stream
renders dashed amber and never counts as done. Detection is forward-only
within a 30-minute window, and never writes the declared stage.

Workspace: one page at /run with a lane grid, the selected lane's pipeline,
and a full Claude console behind a disclosure.
2026-07-30 14:39:03 +07:00

1.3 KiB

description, argument-hint
description argument-hint
Print the orchestration DAG edges (parent→child subagents) for a session. [session-id]

Print the multi-agent orchestration DAG for a session from http://localhost:4820.

The session id is $ARGUMENTS. If empty, fetch curl -s 'http://localhost:4820/api/sessions?limit=1' and use the most recent session, stating which id you picked. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.

Fetch the workflow intelligence and read its orchestration dataset:

curl -s http://localhost:4820/api/workflows/$ARGUMENTS

orchestration contains the DAG nodes (agent id, type, model, status, depth) and parent→child edges.

Print, concisely:

  1. One-line topologyroot → depth <N>, fan-out <max>, <agent count> agents.
  2. Edge list — one line per edge, grouped/ordered by depth: depth d: parent[model] → child[type, status]
  3. Leaves — list the leaf agents (no children) on one line.

No tables, no preamble — just the topology line and the edges. Cite only nodes and edges returned by the API; never invent agents. If the session has no subagents, say so (single-agent session, depth 0). For a rendered tree and depth/fan-out breakdown, point the user at the dag-map skill.