by mag123c
Ultra-fast token & cost tracker for LLM Token Usage (e.g. Claude Code)
# Add to your Claude Code skills
git clone https://github.com/mag123c/toktrackGuides for using cli tools skills like toktrack.
Last scanned: 5/30/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-30T16:06:32.849Z",
"npmAuditRan": true,
"pipAuditRan": true
}No comments yet. Be the first to share your thoughts!
Top skills in this category by stars
30 days in the Featured rail · terms & refunds
English | 한국어
⚠️ Did you know? Claude Code deletes your session data after 30 days by default. Once deleted, your token usage and cost history are gone forever — unless you preserve them.
The token & cost tracker that never loses your history. Most tools re-read your CLI's session files on every run — so when Claude Code deletes them after 30 days, your cost history goes with them. toktrack keeps a persistent cache, so your history survives.
Track usage across all your AI coding CLIs — Claude Code, Codex CLI, Gemini CLI, Qwen Code, OpenCode, and PI Agent — in one dashboard. Built in Rust, so it stays fast even on huge histories (simd-json + rayon).

| Problem | Solution |
|---|---|
| 🗑️ Claude Code deletes data after 30 days — your cost history disappears | 💾 Persistent cache — history survives even after the CLI deletes its files |
| 📊 No unified view — each CLI keeps its own separate data | 🎯 One dashboard — Claude Code, Codex, Gemini, Qwen, OpenCode, PI Agent in one place |
| 🐌 Re-scanning big histories is slow | ⚡ Cached queries in ~0.04s — instant on every run |
daily, weekly, monthly, stats with JSON output supporttoktrack reportNo Rust toolchain required. Downloads the correct binary for your platform automatically.
npx toktrack
# or
bunx toktrack
brew tap mag123c/toktrack
brew install toktrack
cargo install --git https://github.com/mag123c/toktrack
Download from GitHub Releases.
| Platform | Architecture |
|---|---|
| macOS | x64, ARM64 |
| Linux | x64, ARM64 |
| Windows | x64 |
# Launch TUI dashboard
npx toktrack
# Get today's cost in JSON
npx toktrack daily --json
# Monthly summary
npx toktrack monthly --json
toktrack
# Open TUI at specific tab
toktrack daily # Overview (daily view)
toktrack weekly # Overview (weekly view)
toktrack monthly # Overview (monthly view)
toktrack stats # Stats tab
# JSON output (for scripting)
toktrack daily --json
toktrack weekly --json
toktrack monthly --json
toktrack stats --json
# Usage report (shareable receipt)
toktrack report # Last 7 days (text)
toktrack report --month # Last 30 days
toktrack report --days 14 # Last N days
toktrack report --svg # Text + SVG file
# Data-preservation audit (live on disk vs cache-only)
toktrack audit # Per-source coverage report
toktrack audit --json # Machine-readable
Show today's AI spend right in your prompt, updated after every command:
~/projects/api main $12.40
❯
A few lines of zsh/bash/fish — see Shell integration.
toktrack can include Codex session logs from SSH servers by syncing remote JSONL
files into a local snapshot and parsing them with the existing Codex parser. It
uses your existing ssh/rsync setup and never stores SSH passwords or keys.
Create ~/.toktrack/config.toml:
default_remotes = ["devbox"]
[[remotes]]
name = "devbox"
target = "ubuntu@devbox"
[remotes.paths]
codex = "~/.codex/sessions"
[[remotes]]
name = "prod"
target = "prod-alias"
[remotes.paths]
codex = "/home/codex/.codex/sessions"
You can also manage the same config from the CLI:
toktrack remote add devbox ubuntu@devbox --default
toktrack remote add prod prod-alias --codex-path /home/codex/.codex/sessions
toktrack remote default add prod
toktrack remote default remove devbox
toktrack remote remove prod
toktrack remote list
By default, commands read local data plus default_remotes:
toktrack report
toktrack daily --json
Override the configured defaults when needed:
toktrack --remote prod report # local + default_remotes + prod
toktrack --all-remotes stats # local + every configured remote
toktrack --local-only report # local only
Remote Codex sources appear as codex@<remote-name> and use separate cache
files such as ~/.toktrack/cache/codex@devbox_daily.json.
If a remote sync fails, toktrack warns and continues with local data plus any
existing snapshot/cache for that remote.
| Key | Action |
|---|---|
1-4 |
Switch tabs directly (incl. Audit) |
Tab / Shift+Tab |
Next / Previous tab |
j / k or ↑ / ↓ |
Scroll up / down |
Enter |
Open model breakdown popup (Daily tab) |
d / w / m |
Daily / Weekly / Monthly view (Daily tab) |
? |
Toggle help |
Ctrl+C |
Quit |
| CLI | Status | Data Location |
|---|---|---|
| Claude Code | ✅ | ~/.claude/projects/ |
| Codex CLI | ✅ | ~/.codex/sessions/ |
| Gemini CLI | ✅ | ~/.gemini/tmp/*/chats/ |
| Qwen Code | ✅ | ~/.qwen/tmp/*/chats/ |
| OpenCode | ✅ | ~/.local/share/opencode/storage/message/ |
| PI Agent | ✅ | ~/.pi/agent/sessions/ |
| Antigravity | ⚠️ detected, unsupported | ~/.gemini/antigravity-cli/ (no file-readable token usage) |
Costs from sources that don't record their own price (Gemini, Qwen, Codex, and modern Claude logs) are computed from LiteLLM pricing and shown with a
~marker (estimated). Pricing works offline via a bundled snapshot when the network is unavailable.
Each source's data directory can be overridden (matching the upstream CLI's own variable):
| Variable | Source | Default |
|---|---|---|
CLAUDE_CONFIG_DIR |
Claude Code (root) | ~/.claude (+ /projects) |
CODEX_HOME |
Codex CLI (root) | ~/.codex (+ /sessions) |
GEMINI_CLI_HOME |
Gemini CLI (home root) | ~ (+ /.gemini/tmp) |
QWEN_HOME |
Qwen Code | ~/.qwen (+ /tmp) |
OPENCODE_DATA_DIR / XDG_DATA_HOME |
OpenCode | ~/.local/share/opencode |
PI_CODING_AGENT_SESSION_DIR (then PI_AGENT_DIR) |
PI Agent | ~/.pi/agent/sessions |
export CLAUDE_CONFIG_DIR="/path/to/.claude"
Custom pricing (including web_search / web_fetch per-request rates) can be set in ~/.toktrack/pricing.toml.
| Run | Time |
|---|---|
| First run (cold) | ~1.0s |
| Daily use (cached) | ~0.04s |
Measured on Apple Silicon with 2,000+ JSONL files (3.4 GB). The persistent cache means only the current day is recomputed on each run — past days are read straight from cache, so daily use stays instant no matter how large your history grows.
Why it's fast: SIMD JSON parsing (simd-json) + parallel processing (rayon) = ~3 GiB/s throughput on the cold path.
The Problem: You've been using Claude Code for 3 months, spending hundreds of dollars. One day you want to check your total spending — but Claude Code already deleted your session files from 2 months ago. That cost data is gone forever.
toktrack solves this. It caches daily cost summaries independently, so your usage history survives even after the CLI deletes the original files.
| CLI | Default Retention | Policy |
|---|---|---|
| Claude Code | 30 days | cleanupPeriodDays (default: 30) |
| Gemini CLI | Unlimited | opt-in sessionRetention |
| Codex CLI | Unlimited | size-cap only (max_bytes) |
~/.toktrack/
├── cache/
│ ├── claude-code_daily.json # Daily cost summaries
│ ├── codex_daily.json
│ ├── codex@devbox_daily.json
│ ├── gemini_daily.json
│ ├── opencode_daily.json
│ └── pi-agent_daily.json
├── remotes/
│ └── devbox/codex/sessions/ # Synced remote Codex JSONL snapshots
├── config.toml # Optional remote source configuration
└── pricing.json # LiteLLM pricing (1h TTL)
Past dates in each *_daily.json are immutable — once a day is summarized, the cached result is never modified. Only the current day is recomputed on each run. This means even if Claude Code deletes session files after 30 days, your cost history remains intact in the cache.
toktrack audit shows, per source and per day, whether the data is still live (raw session file on disk), cache-only (the CLI deleted the raw file — only toktrack still has it), or missing (no data — an unused day, or one lost before toktrack first saw it; never claimed as a loss).
$ toktrack audit
Data preservation audit (2026-06-08)
claude-code 2025-12-22 → 2026-06-08
live (raw on disk): 79 days
preserved (CLI deleted): 83 days