abtop vs cc-lens
htop for AI coding agents: every Claude Code, Codex and OpenCode session in one TUI — tokens, context-window %, rate limits, child processes, orphan ports. Read-only, no API keys. Rust. — versus — npx cc-lens: local analytics dashboard over ~/.claude — sessions with replay, cost and cache breakdowns, insights and budgets, team-adoption mode, a yearly Wrapped card. No cloud, no telemetry.
Live vs retrospective: abtop shows what your agents are doing right now; cc-lens analyzes what they did — replays, cost/cache breakdowns, budgets. Many desks end up running both.
| abtop | cc-lens | |
|---|---|---|
| Stars | 3.4k | 572 |
| Forks | 302 | 77 |
| Language | Rust | TypeScript |
| License | MIT | MIT |
| Last activity | 16 days ago | 26 days ago |
| Topics | coding | coding |
| Curated connections | 2 | 3 |
abtop — the curator's take
The moment you run 3+ agents in parallel this earns its place: live per-session context-window bars, real-time rate-limit quota, and the sleeper feature — orphan port detection for the dev server an agent forgot to kill. Read-only from local process/file state, cross-platform, Enter jumps to the agent's terminal (tmux/cmux aware). NOT an analytics tool: it's a live dashboard, not history — for cost breakdowns, replays and budgets over time you want a session-log analyzer, not a top. OpenCode monitoring needs the sqlite3 CLI installed.
cc-lens — the curator's take
The zero-friction option among Claude Code dashboards: one npx command, loopback-bound by default, and v0.4's Insights tab actually recommends actions — cache, model choice, compaction, plan-fit and budget opportunities mined from your own usage — instead of just charting it. Team mode (shared-folder push hub + terminal digest) is a real differentiator for leads tracking adoption. Costs are estimates from a local pricing table (`~/.cc-lens/pricing.json` to override) — treat them as directional and keep the table current. Claude-only; for subagent forensics and ticket linking, claude-code-karma digs deeper; for a number next to your clock, ai-token-monitor.