nntrivi2001
57dc91585d
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.
26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
---
|
||
description: Summarize the workflow intelligence for a session — stats, complexity, and top patterns.
|
||
argument-hint: "[session-id]"
|
||
---
|
||
|
||
Summarize the Agent Monitor workflow intelligence 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:
|
||
|
||
```
|
||
curl -s http://localhost:4820/api/workflows/$ARGUMENTS
|
||
```
|
||
|
||
This returns 11 datasets: `stats`, `orchestration`, `toolFlow`, `effectiveness`, `patterns`, `modelDelegation`, `errorPropagation`, `concurrency`, `complexity`, `compaction`, `cooccurrence`.
|
||
|
||
Print, concisely:
|
||
|
||
1. **Header** — session id, total agents, max depth, and total tool calls (from `stats` / `orchestration`).
|
||
2. **Complexity** — the numeric `complexity` score and what drives it (depth, breadth, tool diversity).
|
||
3. **Top patterns** — up to 5 recurring sequences from `patterns`, each as `sequence ×frequency`, sorted by frequency descending.
|
||
4. **Quick signals** — one line each: concurrency lane count (`concurrency`), subagent success rate (`effectiveness`), and total errors with origin depth (`errorPropagation`).
|
||
|
||
Keep it terse — this is a one-shot. Cite only numbers returned by the API; for deeper analysis point the user at the `dag-map`, `delegation-audit`, `concurrency-report`, or `error-propagation` skills.
|