Agents View
Wraps the Research Preview `claude agents` CLI (CC 2.1.139+) and `claude plugin details ork` for live observability of parallel agent sessions. Surfaces running/blocked/done state, per-session token cost, and the 188-hook plugin's runtime footprint. Use when debugging multi-agent workflows, projecting cost on a long-running orchestration, or auditing which hooks fired during a run.
/ork:agents-view/ork:agents-view — Parallel Agent Observability
Research Preview — UI may change before GA. Pinned to CC ≥ 2.1.139.
1. What it does
Thin wrapper around two CC 2.1.139 CLI surfaces:
| Command | Purpose |
|---|---|
claude agents | Research Preview — lists parallel agent sessions with state (running / blocked / done), elapsed time, token usage, and per-session cost projection. |
claude plugin details ork | Plugin runtime footprint — number of hooks loaded, skills available, agents registered, and which hooks fired in the current session. |
Flags:
--plugin— show onlyclaude plugin details ork(skip the agent list).--watch— re-poll every 2s until interrupted (usesclaude agents --watchunder the hood).--json— emit raw JSON for piping into downstream skills (e.g. budget gates).
2. When to use
| Scenario | Why |
|---|---|
Parallel-agent debugging — a /ork:explore, /ork:brainstorm, or /ork:implement run feels stuck | claude agents shows which child session is blocked, on what, and how long. Faster than tailing logs. |
| Observability for the 188-hook plugin | claude plugin details ork reports per-hook invocation counts; useful when a hook is suspected of slowing the loop or firing more often than expected. |
| Per-session cost projection | The Research Preview view ships token + dollar projections per agent. Use before kicking off a long xhigh-effort run. |
Post-mortem after an xhigh orchestration | --json snapshot lets you diff hook fire counts and agent durations across runs. |
3. Sample output
$ /ork:agents-view
claude agents — Research Preview (CC 2.1.139)
─────────────────────────────────────────────
ID AGENT STATE ELAPSED TOKENS COST(proj)
a1f3 ork:explore running 00:04:12 142.3K $0.42
a1f4 └─ ork:backend-system-architect blocked 00:01:08 34.1K $0.09 (waiting: db-schema)
a1f5 └─ ork:frontend-ui-developer running 00:02:55 71.8K $0.21
a1f2 ork:code-quality-reviewer done 00:00:48 18.4K $0.05
─────────────────────────────────────────────
4 sessions · 2 running · 1 blocked · 1 done · projected total $0.77
claude plugin details ork
─────────────────────────
skills: 107 loaded · 12 invoked this session
agents: 37 registered · 4 spawned this session
hooks: 188 total (120 global · 46 agent · 22 skill) · 31 fired
top hooks: skill/repo-structure-indexer (8×) · global/stale-import-detector (5×)--json mode emits the same data as a single JSON object — see claude agents --help for the schema (Research Preview, subject to change).
4. Related Skills
The following skills all spawn background agents that surface in this view — /ork:agents-view is the canonical observability surface for any of them:
ork:brainstorm— multi-agent ideation; check--watchwhile it runs to see which angle is blocking.ork:audit-full— long-running parallel audit; cost projection helps decide whether to let it finish.ork:explore— 4–5 parallel explorer agents;claude agentsshows which explorer is still searching.ork:dev— boots agent-browser as a background session; appears alongside Claude agents in the list.
Anti-patterns
- NEVER parse the human-readable table format — use
--jsonfor any programmatic consumer. The Research Preview output schema is documented; the table layout is not. - NEVER assume
claude agentsis available on CC < 2.1.139 — fall back gracefully and surface the install hint. - NEVER call this inside a tight loop without
--watch; each invocation pays cold-start latency on the CLI.
Agent Orchestration
Agent orchestration patterns for agentic loops, multi-agent coordination, alternative frameworks, and multi-scenario workflows. Use when building autonomous agent loops, coordinating multiple agents, evaluating CrewAI/AutoGen/Swarm, or orchestrating complex multi-step scenarios.
Ai Ui Generation
AI-assisted UI generation patterns for json-render, v0.app, Google Stitch, Bolt Cloud, and Cursor workflows. Covers prompt engineering for component and full-stack app generation, review checklists for AI-generated code, design token injection, refactoring for design system conformance, and CI gates for quality assurance. Use when generating UI components with AI tools, rendering multi-surface MCP visual output, reviewing AI-generated code, or integrating AI output into design systems.
Last updated on