StackMap
Subscribe

abtop vs ai-token-monitor

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 — Menu-bar/tray app for macOS and Windows that reads Claude Code, Codex and OpenCode session logs and shows live token spend — per-model pricing with cache reads, plan-limit bars, webhook alerts.

The curated verdict

Same watch-your-agents job, different surface: ai-token-monitor is a menu-bar app focused on token spend and plan limits; abtop is a terminal TUI adding context-window bars, child processes and port detection per live session.

abtopai-token-monitor
Stars3.4k288
Forks30247
LanguageRustTypeScript
LicenseMIT
Last activity16 days ago5 days ago
Topicscodingcoding
Curated connections25

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.

ai-token-monitor — the curator's take

Zero-setup observability for the coding-agent bill: no API keys, no proxy — it prices the session logs your CLIs already write (cache reads included) and puts today's spend next to the clock, with live 5-hour-session and weekly plan bars that ping Discord/Slack/Telegram before you hit the wall. Offline by default; the leaderboard and chat are strictly opt-in. NOT enforcement or routing — it measures, it doesn't reduce; pair it with a gateway or harness caching fixes when the number scares you. macOS/Windows only, and note the repo currently ships no license file.