Dashbar shows which Claude Code and Codex sessions are working, how much of your plan is left, and which dev servers are idling. Free and open source.
Each Claude Code session by project: working, idle or waiting for you, for how long, and how full its context window is. Click one to go back to the app it runs in. Turn on permission prompts in Settings and a request shows up under its session with Allow once and Deny. The terminal still asks too, and Dashbar never answers by itself.
Your 5-hour and weekly limits, with a mark for where an even pace would be and a projection of when you would run out at the current rate. Each tool has its own card, and the one closest to running out comes first. Codex’s limits come from its own logs. Claude’s come from Claude Code’s status line: add Dashbar to it in Settings and your usage updates after each Claude Code reply, with no network request.
Tokens for Claude Code and Codex today, or over the last 7 or 14 days, by hour or by day, and what they would cost at public API list prices. One choice at the top sets the span for every card, and in the Dashbar window each card also lists its projects and models. The cost is a guide, not your bill, and Settings can hide it. History, in the Dashbar window, keeps 30 days of usage and how full each plan window got.
Dev servers grouped under the project that owns them. One that has been up for over an hour and is barely using the CPU is marked, and so is one an agent started.
CPU, memory, GPU, network and battery, and the busiest apps right now. None of it is new; it is just in the same place as everything else.
Finds node_modules, .next, build folders and Xcode’s DerivedData, shows what you would get back, and moves them to the Trash only after you confirm.
Claude Code and Codex get full support: it reads their session files on your Mac for working status and usage. If you use Google’s agents, Gemini CLI shows its sessions and usage, and Antigravity its sessions, plus usage and plan limits once you add Dashbar to the Antigravity CLI’s status line. Other tools, such as T3 Code, Cursor and Aider, show up as a chip when they are running, without usage numbers. If you want one added, open an issue on GitHub.
Yes. Press Control-Option-D, or the arrow at the top of the panel, to open the Dashbar window: the panel’s pages, History and every running workspace in a sidebar. A workspace’s page shows its uptime, CPU, memory and energy, its dev servers and agents, and the processes behind the numbers. It never starts anything. It acts only when you click: stopping a server, quitting a process after you confirm, or moving a workspace’s caches to the Trash. A pin keeps it on top of other windows.
Yes, two. The small one shows Claude’s 5-hour and weekly limits and when they reset. The medium one shows each tool’s limits (Claude, Codex and Antigravity, when you use them) and how many agents are working. Add them from the desktop: right-click it, choose Edit Widgets and look for Dashbar. macOS refreshes them about every 15 minutes, sooner when Dashbar’s figures change, so they are not live. When Dashbar isn’t running they dim and say since when. They read only the plan limits and agent counts Dashbar saves for them, never project names, folders or sessions.
Yes. The app is universal, so it runs on Apple silicon and on Intel, on macOS 14 or later.
Reading sessions, ports and folders happens on your Mac and costs nothing. The app has no account and no analytics. The only requests are update checks from GitHub, and, if you turn on the experimental way of reading Claude plan limits, one read-only request to api.anthropic.com. If that sign-in has expired, the Refresh button runs Claude Code once in the background, which uses a few tokens. Reading Claude plan limits from Claude Code’s status line sends nothing.
Claude does not save them on your Mac, but after each reply Claude Code passes your 5-hour and weekly usage to its status line (on Pro, Max and Ultra plans). In Settings, under Integrations, Add to Status Line changes one setting in Claude Code’s settings.json, statusLine, to a small script. The script saves just those numbers and the time to a file Dashbar reads, then runs the status line you already had, so it looks the same. Dashbar backs up the settings file first. To undo it, press Remove in the same place, and your previous status line comes back exactly. Nothing is sent and the Keychain isn’t read. The numbers are as fresh as your last Claude Code reply. An older, experimental setting instead reads Claude Code’s sign-in from your Keychain and asks an undocumented endpoint; it is off by default. Codex’s limits come from its own logs and need no setup.
No. It is what your tokens would cost on the pay-as-you-go API at public list prices, worked out on your Mac from the token counts. On a Claude or ChatGPT plan you pay the plan’s price, so treat it as a guide to how much you use. Models without a known price are named rather than counted as $0. Settings, under General, can hide it.
No. Answering permission prompts is off until you turn it on in Settings, under Integrations, which adds one hook to Claude Code’s settings (after a backup; Remove takes it out). Then Dashbar shows what Claude Code wants to do, and answers only when you click Allow once or Deny. Allow once adds nothing to your permission rules. Claude Code keeps its own prompt up in the terminal the whole time, so you can answer there instead. If you don’t answer, Dashbar isn’t running or anything goes wrong, the terminal prompt is the one that counts.
Yes. If you run Claude Code with CLAUDE_CONFIG_DIR or Codex with CODEX_HOME, add each folder in Settings, under Accounts. Dashbar suggests folders like ~/.claude-work that have logs. It reads every account’s sessions and usage, labels them by account, and shows each Claude account’s plan limits from its own status line.
It only looks for caches you can rebuild: node_modules, .next, build folders and Xcode’s DerivedData. It shows what you would get back and moves items to the Trash only after you confirm, so you can put them back.
From version 0.3.0 Dashbar checks for updates itself: open Settings, then About, then Check for Updates. With Homebrew, run brew upgrade --cask dashbar.
If you added Dashbar to Claude Code’s or the Antigravity CLI’s status line, or turned on permission prompts, press Remove for each in Settings, under Integrations, first, so their settings go back to how they were. Then quit Dashbar and drag it to the Trash. With Homebrew, run brew uninstall --cask dashbar, and add --zap to remove its settings, data and caches too.
No. Dashbar is an independent open source project.
For AI agents: this page is also at /index.md as Markdown, and /llms.txt lists the useful links.