vibe-usage CLI
CLI that counts token usage of Claude Code, Codex, Cursor and other agents from local logs and syncs it to vibecafe.ai.
- 147 ★ on the repository
- Last commit
Extended access
Why this level
- Reads local logs and the Cursor token, uploads summaries to an external service and installs a background service.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/vibe-usageDetects 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.
- Reads local logs and the Cursor token, uploads summaries to an external service and installs a background service.
This is third-party code. Review the repository files before installing.
What it does
`vibe-usage` reads local logs of AI tools, totals tokens, cost and sessions and uploads the summary to vibecafe.ai. Sources include Claude Code, Codex CLI and Cursor, with the full table in the README. The first run of `npx @vibe-cafe/vibe-usage` opens a browser for sign-in, saves a key to `~/.vibe-usage/config.json` and turns on background sync every 30 minutes. The `summary` command prints a recent-days summary in Markdown: cost, tokens, tools, models and projects. The `skill` command installs a skill for AI assistants, and `quota` shows remaining subscription quotas for selected products.
Who it is for. Developers using several agents at once who want one view of token usage by day, model and project.
Good fit when
- Tokens flow into Claude Code, Codex and Cursor at once with no combined picture.
- A weekly Markdown summary is wanted for a report: `summary --days 7`.
- The aim is to learn which model or project eats the most.
- Data from several machines is gathered on one vibecafe.ai dashboard.
Not a fit when
- Usage summaries must not go to a third-party service: data goes to vibecafe.ai.
- An offline report is enough: `ccusage` also gives local reports without uploading.
- Background services are forbidden: the first run enables one unless `--no-daemon` is given.
Example request
Show token usage for the last 14 days by tool, model and project.Limitations
The first run without `--no-daemon` installs a background service (systemd, launchd or Task Scheduler) that syncs data every 30 minutes. The summary is uploaded to vibecafe.ai and tied to an account, and the key lives in `~/.vibe-usage/config.json`. For Cursor the tool reads a token Cursor itself saved in `state.vscdb` and calls cursor.com. Token summaries and session metadata are uploaded; the Codex parse cache holds only derived aggregates. For CI, issue a key in advance at `vibecafe.ai/usage/setup` and pass it with `--manual-key`: such a run does not install the service. Some interface messages and help text are in Chinese.
How to disable. Run `npx @vibe-cafe/vibe-usage daemon uninstall` to remove the background service. The key and cache sit in `~/.vibe-usage/` and are deleted by hand.
FAQ
How do I connect on a machine without a browser?
Issue a key at `vibecafe.ai/usage/setup` and run `npx @vibe-cafe/vibe-usage init --manual-key vbu_... --no-daemon`. This works in CI and over SSH.
How do I turn sync off?
With `npx @vibe-cafe/vibe-usage daemon uninstall`. To never get the service, add `--no-daemon` to the first run.
Which agents are supported?
See the Supported Tools table in the README: among them Claude Code, Codex CLI, Cursor, Trae CLI and WorkBuddy.
What does `summary` print?
A Markdown summary for 7 days by default. The `--days N` flag sets a period from 1 to 90 days.
How do I check state?
`npx @vibe-cafe/vibe-usage status` shows configuration, detected tools and what has been uploaded.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI that analyzes Claude Code and Codex sessions: standup summary, productivity report and tips in the status line
Token and cost reports for Claude Code, Codex, Gemini CLI and other agents from local logs, by day, month and session
An MCP server and CLI that submit ccusage stats to a shared AI coding spend leaderboard and let the agent read the board.
A limits and token spend monitor for Claude Code, Codex, Antigravity and Grok CLI: macOS menu bar, Windows tray, HTML reports
TokenTracker counts tokens and spend across Claude Code, Codex, Cursor, Gemini CLI and other agents from local logs and shows them on a local dashboard
Counts token use and cost of Claude Code and Codex sessions from local logs and shows remaining limits in the status line
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| vibe-usage (this card) | no | 147 | |
| ccusage | no | 19,337 | ccusage builds reports from local logs; vibe-usage additionally syncs them to the vibecafe.ai dashboard and runs as a background service |
| Claude Usage | no | 2,286 | claude-usage shows a local dashboard of Claude Code logs; vibe-usage combines many agents and machines |
README in short
Upload is incremental: after a full local snapshot only new or changed summaries are sent, so a quiet machine uploads nothing. Data is gzip-compressed.