abtop vs agent-orchestration-standard
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 — Read-only live monitor for Claude Code: a streaming graph of sessions, subagents, tokens, cost, file conflicts and alerts, as plugin, TUI and MCP server. Ships the AOS-1 spec.
Both are live monitors of coding-agent sessions. abtop is an htop-style TUI across Claude Code, Codex and OpenCode.
| abtop | agent-orchestration-standard | |
|---|---|---|
| Stars | 3.8k | 103 |
| Forks | 344 | 22 |
| Language | Rust | JavaScript |
| License | MIT | MIT |
| Last activity | 1 months ago | 2 days ago |
| Topics | coding | orchestration, coding |
| Curated connections | 10 | 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.
agent-orchestration-standard — the curator's take
Use it to watch what parallel Claude Code sessions and subagents are doing right now, with replay and alerts, at no install cost (no dependencies). Despite the name, it does not orchestrate anything: that is a separate experimental repo. Active development has moved to Fenceline, so this repo may go stale. Claude Code only.