vibetracking
v0.2.4
Published
Track AI coding assistant token usage and costs across Claude Code, Codex, Cursor, and more.
Maintainers
Readme
vibetracking
Track AI coding assistant usage across Claude Code, Codex, Cursor, Gemini, Amp, and more.
Requirements
- Bun >= 1.0
Installation
# One-off execution
bunx vibetracking
# Global install
bun add -g vibetrackingUsage
# Run - scans local data and opens browser to import
vibetracking
# Sync data (alias of vibetracking)
vibetracking sync
# Login (handled in browser during import)
vibetracking login
# Check CLI auth status
vibetracking whoami
# Logout (clears local cache only)
vibetracking logoutCursor Integration
# Open Cursor export page (login in browser if needed)
vibetracking cursor login
# Check Cursor cache status
vibetracking cursor status
# Clear cached Cursor data
vibetracking cursor logoutSupported Tools
| Tool | Data Location |
|------|---------------|
| Claude Code | ~/.claude/projects/ |
| Codex | ~/.codex/ |
| OpenCode | ~/.local/share/opencode/ |
| Gemini | ~/.gemini/ |
| Amp | ~/.ampcode/ |
| Cursor | Browser CSV export (requires login) |
How It Works
- Scan: Vibetracking scans your local AI coding tool data
- Parse: Native Rust module parses session files in parallel
- Calculate: Estimates costs using real-time model pricing from LiteLLM
- Import: Opens browser to import data to vibetracking.dev
- Share: View your stats, compare on leaderboards, share your profile
Links
- Website: https://vibetracking.dev
- GitHub: https://github.com/lfglabs/vibetracking
License
MIT
