ccboard CLI
A terminal and web dashboard for Claude Code sessions, costs and settings, with budget alerts and a 30-day forecast.
- 101 ★ on the repository
- Last commit
Extended access
Why this level
- Reads local logs of all sessions, and `ccboard setup` edits `~/.claude/settings.json`.
- The install script from the README runs through `curl | bash`.
Install
- Works in
Manual install
brew tap FlorianBruniaux/tapThe first install command from the README, followed by `brew install ccboard`.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads local logs of all sessions, and `ccboard setup` edits `~/.claude/settings.json`.
- The install script from the README runs through `curl | bash`.
This is third-party code. Review the repository files before installing.
What it does
ccboard, a Rust program, reads local Claude Code data from `~/.claude` and builds a dashboard: a terminal interface by default and a web mode through `ccboard web`. Tabs show sessions, tokens and cost by model, day and project, searchable history, hooks, agents, skills and MCP servers. The `ccboard setup` command adds hooks to `~/.claude/settings.json`, so the dashboard sees which session is running, which waits for permission and which has finished. Budget alerts and the forecast come from its own SQLite cache. Cursor, Codex CLI and OpenCode sessions load alongside when those tools are installed.
Who it is for. Developers who work in Claude Code daily and want token spend, budget and the state of parallel sessions in one place.
Good fit when
- The monthly Claude Code bill grew, and spend is broken down by project and model.
- Several sessions run at once, and it matters which one waits for permission.
- An old agent conversation is found by its text and opened in full.
- Hooks, MCP servers and skills are compared across settings at different levels.
Not a fit when
- Session logs hold private code and an extra database is unwanted: the cache and Brain notes live on disk.
- A one-off token report is enough: `ccboard stats` or a narrower utility will do.
- Hooks in `~/.claude/settings.json` must stay untouched: `ccboard setup` adds its own entries.
Example request
Install ccboard, run `ccboard stats` and summarize which projects spent the most tokens this month.Limitations
macOS is the best-tested platform. Linux passes CI checks and Windows support is experimental. Installing with `cargo install` builds a binary without the web interface: `ccboard web` needs Homebrew, the install script or a prebuilt binary from releases. Cost in the panel stays an estimate based on tokens from local logs. The last commit in the repository is dated September 2026.
How to disable. Remove the hooks added by `ccboard setup` from `~/.claude/settings.json`, then remove the binary the way you installed it. Delete the cache and notes database in `~/.ccboard/` by hand.
FAQ
How do I open the dashboard in a browser?
Run `ccboard web --port 3333`. The `ccboard both --port 3333` command starts the terminal and web interfaces together.
Does it need configuration?
No, it reads `~/.claude` right away. Live session status is enabled by a separate `ccboard setup` command that adds hooks.
Which agents besides Claude Code appear?
Cursor, Codex CLI and OpenCode: sessions import when the tool is installed. The other tabs are built around Claude Code.
Why is the web interface empty after `cargo install`?
The crates.io build omits the WASM part. For `ccboard web` use Homebrew, the install script or a binary from releases.
What does the Brain tab store?
Notes across sessions. The stop hook writes progress, decisions and blockers to `~/.ccboard/insights.db`, and a new session start injects what is relevant.
Discussion
No questions or reviews yet.
Related
CLI toolsA dashboard for every Claude Code session on the machine: live agents, cost, history search and MCP tools for Claude.
A local dashboard for Claude Code sessions: timelines, token costs, tools, agents, skills and live sessions
A local real-time dashboard for Claude Code and Codex sessions: agent activity and tool calls
A top-style terminal dashboard for Claude Code and Codex sessions: spend, tokens, context load, processes and tool calls.
Terminal monitor for Claude Code sessions: busy state, remaining context, memory, processes and sessions waiting for you.
ClawMetry reads the session files agents already write and shows the timeline, tool calls, tokens and cost in one dashboard.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| ccboard (this card) | no | 101 | |
| ccusage | no | 19,415 | prints token and cost reports; ccboard adds an interface with settings, hooks, MCP and live session status |
| agentsview | no | 6,431 | browses sessions in a web interface; ccboard also runs in the terminal, keeps budget alerts and manages hooks |
README in short
The README lists 14 interface tabs, a 224 ms start after the SQLite cache warms up and a binary of about 5.8 MB. It also covers live session status through hooks and import of Cursor, Codex CLI and OpenCode sessions.