KeysrsKeysrs vs ccusage vs CodexBar
What's the short answer?
Use ccusage for token and cost reports in a terminal on any OS. Use CodexBar for live plan limits across many providers, if you're fine with it reusing your provider logins. Use Keysrs for Claude Code, Codex and Grok limits from local files only, plus a Touch ID vault for your API keys.
What does each one do?
- ccusage is a command-line tool that reports token usage and cost from local logs. It needs Node or Bun, is MIT-licensed, and covers Claude Code, Codex, Gemini CLI, Grok Build CLI and many other coding agents. Its
blocksreport groups Claude Code usage into five-hour windows worked out from the logs. - CodexBar is a macOS 14+ menu bar app, with a CLI, widgets and a Linux desktop app. It is MIT-licensed and covers dozens of providers, including Codex, Claude, Cursor, Gemini and Copilot. It shows the session, weekly and monthly limits the providers report, with reset countdowns.
- Keysrs is a macOS 14+ menu bar app for Apple Silicon, MIT-licensed. It shows Claude Code, Codex and Grok plan windows, charts tokens and estimated list-price cost, and keeps API keys in the Keychain behind Touch ID with a scoped local gateway.
Where does each one get its numbers?
- ccusage reads local files. It fetches model prices from LiteLLM and models.dev unless you run it with
--offline(cost modes). - CodexBar mostly asks the providers. For Codex it reads the OAuth token in
~/.codex/auth.jsonand calls ChatGPT's usage endpoint (Codex docs). For Claude it uses Claude Code's stored OAuth credentials, the CLI, or claude.ai browser cookies (Claude docs). For Cursor it uses browser session cookies. That is why its limits are current: they come straight from the provider. - Keysrs reads only the files the tools write: Claude Code's usage cache, Codex session logs and Grok's logs. It never reads auth files or cookies and never visits provider websites. The limits are the ones the tools last saved, so they are only as fresh as your last session, unless you turn on Keep Claude Limits Fresh, which runs Claude Code's own
/usage.
Which one stores API keys?
Only Keysrs has a vault. CodexBar can store provider API keys in a config file with restricted permissions, but only to query usage (README). ccusage has no key storage.
When is ccusage the better pick?
When you want reports rather than a menu bar: daily, monthly, per-session or per-project, as JSON, on Linux or Windows, with nothing to install beyond npx ccusage@latest. It also covers far more coding agents than Keysrs.
When is CodexBar the better pick?
When you use Cursor, Copilot, Gemini or other tools Keysrs doesn't track, want limits that are always current, want widgets or Linux, and are comfortable with an app that reuses your provider logins and cookies to fetch them.
When is Keysrs the better pick?
When you mostly use Claude Code, Codex and Grok, want nothing read beyond the files those tools write, and also want your API keys out of .env files and behind Touch ID.