cobusgreyling

Claude Code Agent View Demo — Development skill for Claude Code

Development community

Web companion dashboard for Claude Code Agent View — live status, telemetry, and per-session post-mortem.

How to install Claude Code Agent View Demo

This entry records only its repository, not the path inside it, so there is no exact command to give. Open cobusgreyling/claude-code-agent-view-demo and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Code Agent View Demo does

Web companion dashboard for Claude Code Agent View — live status, telemetry, and per-session post-mortem.

Alternatives in Development

Claude Balancer — A load balancer proxy for multiple Claude OAuth accounts with automatic failover, request tracking, and web da 910 ★
Maestro Session Manage — Manage a v3 Session — inspect status/resume-view, review knowledge candidates, complete, archive/unarchive 530 ★
M5 Paper Buddy — 📟 Claude Code physical companion on M5Paper V1.1 e-ink 160 ★

README

Agent View Web

![Agent View Web — dashboard with post-mortem drawer](images/hero.jpg)

Web companion for Claude Code's `claude agents` Agent View — same rows, one extra column the TUI doesn't show, and a per-session **post-mortem drawer**.

Agent View tells you *what is running*. This tells you *what each session has cost, how many tools it has burned, and exactly what it did*.

What it does

Live table of every background session in ~/.claude/jobs/ — status, name, intent, idle time, branch.
Telemetry columns — tool calls, input/output tokens, cost, model. The column Agent View should have.
Post-mortem drawer — click any row. Get the full state timeline, every tool call with arguments, every file touched, total duration, a cost breakdown, and the cumulative git diff since the session started.
Persistent archive — completed sessions are snapshotted into SQLite the moment they reach a terminal status, so the dashboard still has them after ~/.claude/jobs// is purged. Archived rows show up in the live table tagged with an archived pill.
Stop a session from the drawer — drops a STOP sentinel the supervisor picks up.
Per-message cost — sessions that mix models (Haiku for compaction, Sonnet/Opus for the loop) get billed correctly per message.
Search / filter / rollup — /api/sessions?status=…&branch=…&since=…&limit=&offset= and /api/summary (with the same filters) for cost-by-day, by-branch, by-model.
Live updates over SSE — the dashboard subscribes to /api/sessions/stream; the stream honours the same filters and ships a heartbeat so proxies don't kill it. Polling is the fallback.
LAN-reachable with auth — --bind exposes it on 0.0.0.0 and requires a token; triage from your phone without leaking transcripts.

No daemon. One small SQLite file alongside `~/.claude/` to hold the archive — opt out with `AGENT_VIEW_DB=off`. Otherwise reads the same on-disk state the supervisor writes; nothing is cap