Files
AgentHub/plugins/agenthub-workflows/commands/dag.md
T
nntrivi2001 17d56d0e01 refactor!: rebrand CCAM to AgentHub
Clean break, no compatibility alias. Renames the product name, the CLI
binary (`ccam` -> `agenthub`), the env var prefix (`CCAM_` ->
`AGENTHUB_`), the Prometheus metric namespace (`ccam_*` ->
`agenthub_*`), the tmux session prefix (`ccam-lane-<id>` ->
`agenthub-lane-<id>`), the per-repo runtime profile directory
(`.ccam/profile` -> `.agenthub/profile`), the lanes state root
(`~/.claude/ccam-lanes` -> `~/.claude/agenthub-lanes`), the bundled
plugins (`plugins/ccam*` -> `plugins/agenthub*`) and their slash
commands (`/ccam-doctor` -> `/agenthub-doctor`, `/ccam:*` ->
`/agenthub:*`).

Because there is no alias, an existing install has to be updated by
hand: rename its `.ccam/profile` directory and any `CCAM_*` variables,
and reinstall the plugin under its new name.

Two other name families are deliberately left alone here, since they are
not just strings: the `Claude-Code-Monitor` repository/marketplace name,
and the `agent-dashboard` npm package plus its `~/.claude/agent-dashboard`
runtime directory, which holds the live database and needs a migration
rather than a rename.

Verified: server 1406/1406, client 459/459, `grep -i ccam` clean across
tracked files, `openapi.yaml` regenerated (95 paths, unchanged count).
2026-09-07 12:09:15 +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 topology — root → 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.