token-tracker
Claude Code & Codex 本地 token 追踪, 状态栏(Codex 业界首创伪 statusline)、GitHub 风格热力图、多模型成本分析。 | Local token tracker for Claude Code & Codex, status line (industry-first Codex faux statusline), GitHub-style heatmap, multi-model cost analysis
Runssource: GitHubPythonMITcommit 85a6b573bb53
Python, MIT licensed. The project labels itself: ai agent, anthropic claude, claude code, cli, codex, cost analysis, developer tools and openai codex.
token-tracker runs. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Installed per install.sh into a private venv; all 416 repo tests pass, and tt --version, tt setup, tt theme, tt status, tt daily, tt weekly, tt monthly, tt sessions, and tt sidebar --once all exit 0 and render live Codex data from this container.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
- Install time
- under a minute
- Cold machine to finish
- 1 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pytest: 416 passed in 4.53s; tt --version printed 'token-tracker 0.5.9'; tt status/daily/weekly/monthly/sessions/sidebar --once/theme/setup all exited 0 and rendered real data from ~/.codex/sessions (155.4K tokens, 1 session, deepseek-v4-flash, sidebar listed this live session)
- Model tokens used
- 48,863
- Exact commit tested
- 85a6b573bb53
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
setup RC=0 === lrwxrwxrwx 1 runner runner 51 Oct 18 22:16 /home/runner/.local/bin/tt -> /home/runner/.local/share… -rwxrwxr-x 1 runner runner 256 Oct 18 22:16 /home/runner/.local/share/token-tracker/venv/bin/tt questionary 2.1.1 rich 15.0.0 textual 8.2.8 token-tracker 0.5.9 All checks pass. The install is the documented flow (`install.sh` → private venv → PyPI wheel `toke… tokens used 48,863 All checks pass. The install is the documented flow (`install.sh` → private venv → PyPI wheel `toke…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.1 minutes, faster than the median of the 83 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 84 ai-agent projects Argusic has installed and timed, token-tracker was the 5th fastest to reach a running state, and 58 of 84 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.1 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
ai-agentanthropic-claudeclaude-codeclicodexcost-analysisdeveloper-toolsopenai-codexpythonstatuslineterminal-uitoken-trackerusage-tracking
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/token-tracker)Questions
- Does token-tracker run?
- Yes. token-tracker runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test token-tracker?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 85a6b573bb53. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test token-tracker?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does token-tracker take to install?
- 0.1 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does token-tracker need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing token-tracker?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does token-tracker compare with the alternatives?
- Of the 84 ai-agent projects Argusic has installed and timed, token-tracker was the 5th fastest to reach a running state, and 58 of 84 reached one at all.
- Where is the evidence for token-tracker?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.