cctop
Like htop, but for Claude Code. A live terminal dashboard that shows all your sessions at a glance, status, context usage, tokens, and latest messages.
Install
Requires Claude Code, uv, and jq.
curl -fsSL https://raw.githubusercontent.com/DeanLa/cctop/main/install.sh | bash
Then launch from any terminal:
cctop
Why
If you're past the "one session at a time" stage but not running a fleet of headless agents, you're in the middle ground where most tools don't help. You have 4-20 sessions open across multiple projects, refactoring one repo while tests run in another, firing off a prompt in a third while waiting for a fourth to finish. You context-switch constantly, lose track of which tab is blocked on you, and forget what that session in the background was even doing.
cctop gives you one screen to see all of them.
What You See
Keybindings
| Key | Action |
|---|
q | Quit |
r | Force refresh |
R | Purge dead sessions (PID check + staleness fallback) |
s | Open sort picker (activity, name, status, duration, turns, tokens, tools, files, agents, errors) |
ctrl+p | Open command palette (switch theme, etc.) |
Columns
| Column | What it shows |
|---|
| Name | Session display name (custom title or directory slug) |
| Project | Working directory name |
| Branch | Git branch (truncated to 20 chars) |
| Status | Granular activity status (see below) |
| Model | Model family and version (e.g. "sonnet 4.6", "opus 4.6") |
| Ctx% | Context window usage percentage |
| Tokens | Total tokens consumed (e.g. "145k") |
| Tools | Tool call count |
| Files | Number of files edited |
| Agents | Running subagents |
| Errors | Error count (highlighted in red) |
| Turns | Conversation turn count (user-assistant exchanges) |
| StopRsn | Last stop reason (done, tool, limit) |
| Duration | Elapsed time since session start (e.g. "1h23m") |
| Started | Session start time (e.g. "14:30") |
| Activity | Time since last event (e.g. "2m ago") |
Highlight any row to see a detail panel with the full working directory, git branch, token breakdown, files edited, subagent and error counts, the last user prompt, and Claude's last response.
Status Labels
The Status column shows what each session is doing right now:
| Status | Color | Meaning |
|---|
| idle | green | Waiting, no action needed |
| awaiting plan | blue | Plan ready for your review |
| needs input | orange | Blocked on a question from Claude |
| awaiting permission | orange | Waiting for you to approve a tool use |
| thinking | yellow | Claude is generating a response |
| planning | blue | Session is in plan mode (reading/searching for the plan) |
| editing | orange | Writing or editing files |
| running cmd | green | Executing a shell command |
| searching | cyan | Searching files (Glob/Grep) |
| reading | cyan | Reading files |
| searching web | magenta | Web search or fetch |
| subagent | purple | Running a subagent |
| reviewing | purple | Running a code review subagent |
| researching | purple | Running an explore/research subagent |
| mcp:server | magenta | Using an MCP tool (e.g. mcp:atlassian) |
| error: type | red | Hit an error (rate limit, auth failed, etc.) |
| stale | dim | No activity for 1+ hour |
Session Lifecycle
Sessions that go quiet for 1+ hour are marked stale. Sessions that end clean up after themselves. Sessions whose Claude process has exited (e.g. Ctrl+C) are automatically removed by the background poller via PID checks. Press R to manually purge dead sessions, or run cctop --reset to wipe all session data and start fresh.
A health check bar may appear at the bottom of the dashboard when cctop detects a mismatch between tracked sessions and running Claude processes. This is normal if you had sessions running before installing cctop.
Configuration
cctop stores settings in ~/.cctop/config.toml. All settings are saved automatically as you use the dashboard:
[ui]
theme = "textual-dark" # any Textual built-in theme (ctrl+p to change)
[sort]
column = "activity" # column key to sort by
reverse = true # sort direction
[columns]
hidden = [] # list of hidden column keys
Theme, sort, and column visibility all persist across restarts. The --reset flag clears session data but preserves your config.
Troubleshooting