abtop CLI
A terminal monitor for Claude Code, Codex CLI and OpenCode sessions: tokens, context window, rate limits and ports in real time
- 3,847 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Runs as a terminal dashboard reading processes, ports and agent session state files
- Sends nothing out and needs no keys
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/abtopDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs as a terminal dashboard reading processes, ports and agent session state files
- Sends nothing out and needs no keys
This is third-party code. Review the repository files before installing.
What it does
abtop puts every running agent session on one terminal screen, in the style of htop. It reads local process and session-file state and shows token usage, context window fill percentage, rate limit status, child processes and open ports for each session. The tool only reads local data, makes no external API calls and needs no keys. From the list you can jump straight into the session's terminal pane via tmux, cmux or iTerm2.
Who it is for. For developers who run several Claude Code, Codex CLI or OpenCode sessions at the same time.
Good fit when
- You run several agent sessions across projects and lose track of them
- You need to catch a rate limit or a filling context window before it stalls you
- An agent left a server or port running and you need to find it
Not a fit when
- You only ever run one agent session at a time
- You need historical metrics over past days, not a live snapshot
Example request
Show me how many tokens my open Claude Code sessions have used right nowLimitations
OpenCode monitoring on Linux and Windows needs sqlite3 available in PATH. Windows does not report system load average. The tool only sees sessions for which the relevant agent's local state files are accessible.
How to disable. Remove the abtop binary (cargo uninstall abtop, or delete the file), and if you ran --setup, revert the installed rate limit collection hook.
FAQ
Do I need API keys?
No, abtop only reads local process and session files, sends nothing anywhere and needs no authorization.
Which agents are supported?
Claude Code, Codex CLI and OpenCode. Some features, like subagent tracking, are available only for Claude Code.
Discussion
No questions or reviews yet.
Related
CLI toolsStreams Claude Code hidden thinking, tool calls and subagents to a separate terminal with a live session tree
A desktop GUI app for Claude Code: session management, custom agents and a token cost dashboard
A TUI that shows what Claude Code, Codex, Gemini CLI and opencode do in a project: the open file, last-commit diff, live commands
A macOS terminal with the termio CLI and a skill: agents spawn sibling sessions and you see which one needs your answer
Session monitor for Claude Code, Cursor, Codex and six more agents in a terminal, window or HTTP API, with chat cleanup and search
A terminal and browser viewer for coding agent spend: sessions by turn, subagent and context window, with API price estimates.
README in short
The README describes abtop as a btop-style dashboard for AI coding agents: a TUI panel shows tokens, context window percentage, rate limits, git status, child processes and ports for each Claude Code, Codex CLI and OpenCode session. It ships an installer for macOS, Linux and Windows, a cargo package, prebuilt release binaries, 12 themes, and an Enter-to-jump shortcut into the right terminal pane via tmux, cmux or iTerm2 on macOS.