mrkeyoor.comAsk

xiufengsun/TokenTrackertested 30 Sept 2026commit daa6c55

TokenTracker review

TokenTracker is worth evaluating for personal usage trends if you want a dashboard and desktop views across coding tools.

  • Install 10 s
2,690/2,726passed, run exited non-zero
  • 60 packages
Dev Toolsevaluationupdated 24 Oct 2026
+18stars / 7d

TokenTracker combines AI coding-tool usage records in a local dashboard for tokens, estimated cost, quotas, and activity. The supplied current README advertises 46 supported tools; the README at our measured commit advertised 42. Those are upstream integration counts, not integrations we tested. Desktop apps, widgets, cloud sync, and a public leaderboard are also documented.

Verdict

TokenTracker is worth evaluating for personal usage trends if you want a dashboard and desktop views across coding tools. Its documented cost estimates need reconciliation before financial use. Our 2026-09-30 run at daa6c55 confirmed successful dependency setup and a test command that exited 1; it did not verify CLI installation, desktop operation, billing accuracy, or current-release behavior. The historical OmO report is now closed through a linked fix, so it should not be presented as an unresolved current defect. Start with the integrations you actually use and compare their totals with provider records.

We ran it

Lab card: what happened when we ran TokenTracker
Lab card from our sandbox run
Screenshot of TokenTracker (www.tokentracker.cc)
www.tokentracker.cc
Install✓ · 10s60 packages · 43 MB
Buildn/ano build script
Tests✗ · 78s2690 passed · 36 failed of 2726 (node:test)
Known vulns00 critical · 0 high · 0 moderate · 0 low (npm audit)
Repo1343 files~312,411 lines of source · 29.6 MB · 11 CI workflows · tests dir

Answers from our run

Does TokenTracker build from source?

Dependencies installed in 10 seconds (60 packages), and the project has no separate build step. We cloned commit daa6c55 into a clean Debian container with 3 CPUs and no project-specific setup.

Do TokenTracker's tests pass?

No. The project's own test command finished in 78 seconds and reported 2690 passed, 36 failed (node:test).

Does TokenTracker have known vulnerabilities in its dependencies?

npm audit found none in the dependency tree at the time of our run.

Who should not use TokenTracker?

Finance teams needing reconciled billing records: we did not measure agreement with provider invoices, and the README documents estimated and unpriced usage.

What are the alternatives to TokenTracker?

ccusage, Tokscale. TokenTracker is worth evaluating for personal usage trends if you want a dashboard and desktop views across coding tools.

Setup3/5The README provides a short setup path and platform guidance. Our dated dependency step succeeded with engine and deprecation warnings, but CLI launch, hooks, dashboard operation, and desktop setup were not verified.
Docs4/5The supplied README explains collection methods, commands, network activity, estimates, platform caveats, and cleanup. Those detailed instructions were not fully exercised in our run.
Community3/5The supplied issues show substantive maintainer replies, an OmO fix linked to closure, and continuing Kaspersky tracking through October 24. This supports visible maintenance, not a measured adoption level or response-time guarantee.
Maturity2/5Our historical test command exited 1, no build or application workload was verified, and supplied documentation identifies estimation and platform constraints. Later issue progress does not substitute for a current reliability check.

Who it’s for

Developers using several AI coding tools who want a personal view of usage and estimated cost.
Readers who prefer a browser dashboard or desktop widgets to terminal reports.
Developers willing to compare each integration's totals with provider records before relying on them.

Who it’s NOT for

Finance teams needing reconciled billing records: we did not measure agreement with provider invoices, and the README documents estimated and unpriced usage.
Environments that prohibit reading coding tools' local files, changing hook configuration, or reusing stored credentials for quota requests.
Teams requiring verified desktop signing, antivirus compatibility, or a passing current test suite before deployment. Our stored run and the supplied issue reports do not establish those conditions.

Setup reality

In our recorded run on 2026-09-30 at commit daa6c55099d34458ff773f6c1edd777f16fb7693, the dependency-install step exited successfully in 10.153 seconds. The stored summary records 60 dependencies and 43 MB, while its retained output says 48 packages were added in 4 seconds. These are different recorded scopes and have not been reconciled. This was dependency setup, not a verified installed-CLI or dashboard check.

The install output identifies Node v20.20.2 and npm 10.8.2, despite the configured image label lab-node:22. It warns that undici@8.10.2 requires Node >=22.19.0 and that prebuild-install@7.1.3 is deprecated. The recorded npm audit advisory total is zero; scan coverage is unknown, and that result is not a safety assessment.

The harness skipped its build step with reason "no script". That does not mean the project has no build process: the recorded scripts include dashboard:build, and the commit README documents a dashboard build. The test step exited 1 after 77.748 seconds. Its retained footer reports 2,759 tests, 2,690 passes, 36 failures, and 33 skips; the parser summary's 2,726 equals passes plus failures. We have not reconciled a complete log or verified exhaustive unique coverage.

The README requires Node.js 20+ and documents npx tokentracker-cli for first-run hook setup, sync, and dashboard launch. That command was not verified by our recorded dependency-install step. The documented default address is localhost:7680, with port fallback and a WSL default of 7681 described at the measured commit. Debian 12 users are directed to AppImage, and GNOME needs an AppIndicator extension for the tray.

A dashboard for personal usage, with accuracy to check

TokenTracker puts usage from several AI coding tools in one place. The decision is whether its dashboard and desktop views help you understand your own activity, and whether the integrations you use agree closely enough with provider records.

The supplied current README advertises 46 supported tools. At our measured commit, daa6c55, the README advertised 42. Neither number measures our integration coverage. Upstream documents hooks, plugins, local SQLite databases, session logs, and some provider API requests as collection methods.

The documented interface includes a browser dashboard, native apps for macOS, Windows, and Linux, four desktop widgets, a pixel pet, and 15 achievement tracks. tokentracker status --json supplies machine-readable status. Usage is documented as aggregated into 30-minute UTC buckets in local SQLite. We did not exercise these interfaces or measure a coding workload.

What our recorded run establishes

Our stored run began on 2026-09-30 at 12:10:19.187 UTC using commit daa6c55099d34458ff773f6c1edd777f16fb7693. Its recorded configuration was 3 CPUs, 8 GB of memory, and image lab-node:22. The actual install output identifies Node v20.20.2 and npm 10.8.2; the image label does not establish the runtime version.

The dependency-install step exited 0 after 10.153 seconds. The summary records 60 dependencies and 43 MB, but the retained command output says 48 packages were added in 4 seconds. We cannot explain that difference from the retained record. Successful dependency setup does not establish that a packaged CLI was installed, hooks worked, or the dashboard launched.

The output also contains an engine warning: undici@8.10.2 requires Node >=22.19.0. It reports prebuild-install@7.1.3 as deprecated. These warnings qualify the successful exit; they do not establish a runtime failure or explain the test failures.

The recorded npm audit advisory total was zero across critical, high, moderate, and low severities. Coverage is unknown. This result does not establish that TokenTracker is safe, that all dependencies were assessed, or that desktop artifacts were examined.

The harness skipped its build step with reason "no script". The repository nevertheless records a dashboard:build script and platform build scripts. The commit README also documents building the dashboard. No build was verified in our run.

The test command exited 1 after 77.748 seconds, rounded to 78 seconds in the summary. Its retained node:test footer reports 2,759 tests: 2,690 passed, 36 failed, and 33 skipped. The stored parser total of 2,726 is the sum of passes and failures, excluding skips. These are recorded summary counts, not independently reconciled exhaustive unique coverage. Skipped tests were not failures.

The retained tail names test/zed-parser.test.js as a failing test file and includes generic test-failure messages. It does not establish every failure's cause. A failed command at this historical commit cannot establish that the current product is broken.

For context, the stored checkout metrics were 1,343 files, approximately 312,411 source lines, and 29.6 MB, with 11 CI workflow files, a tests directory, and no Dockerfile or Compose file. Those measurements describe repository shape, not product reliability.

Setup changes local configuration and can make network requests

The README requires Node.js 20+ and documents npx tokentracker-cli as the quick start. Upstream says first run installs managed hooks, syncs records, and opens the dashboard at localhost:7680. The measured-commit troubleshooting section documents automatic port fallback and a default of 7681 under WSL. These are documented behaviors, not launch results from our run.

Use tokentracker status to inspect integration state and doctor for the documented health check. The documented tokentracker uninstall command removes managed hooks and local TokenTracker configuration and data. Passive readers inspect files the coding tools already create; hook and plugin integrations can change those tools' configuration.

Local processing does not imply offline operation. The current README lists provider quota checks using existing credentials, update checks, GitHub star counts, pricing refreshes, a daily heartbeat, and PostHog page views. It also lists optional Sentry error reports when a DSN is configured. TOKENTRACKER_NO_TELEMETRY=1 or DO_NOT_TRACK=1 disables anonymous telemetry according to upstream; those settings do not disable every documented network request.

The README says prompts, responses, and code are not saved or uploaded by the tracking path. We did not audit that implementation or capture network traffic. Treat it as an upstream privacy statement.

Cloud sync and leaderboard participation are optional. The current README distinguishes free local features from the officially hosted TokenTracker Cloud service, which it lists at USD 4.99 per month or USD 39.99 per year before checkout tax. It describes the complete self-hosted installation as a technical preview. Those current terms should not be inferred from the historical dependency run.

Cost estimates need provider-level reconciliation

Upstream explicitly describes Grok cost as estimated because local telemetry lacks a stable prompt, output, and cache split. It also says models without published pricing can show $0. For Devin models without pricing data, the README explicitly warns that a $0 figure does not mean free usage. A dashboard dollar total therefore needs context before it becomes a financial record.

The OmO report concerns TokenTracker v1.1.3, with the reporter first noticing the behavior on v1.1.0. It describes Anthropic-subscription requests appearing in both OmO and Claude records. On October 1, the maintainer acknowledged the reader's overlap limitation and said there was no shipped fix yet. The supplied issue history subsequently records closure as completed through PR #788 on October 13, referencing commit 10f0a23. That is evidence of a linked fix, not our verification of a released binary or every overlap case.

The supplied Kiro report concerns embedded CLI v1.0.7 and is also marked closed. Its discussion documents an undercounting estimator and uncertainty about reconstructing request input from context percentages. The supplied extract does not establish the closing change or a verified replacement estimator. We cannot describe that historical report as an open current defect or claim that current Kiro totals are exact.

Neither report came from our sandbox test command. We did not compare TokenTracker totals with invoices, subscription credits, or provider usage exports. Before using the totals for reimbursement or chargebacks, reconcile the relevant integration with authoritative records.

Desktop packaging needs a separate check

The README directs Debian 12 users to the roughly 120 MB AppImage because the .deb depends on libappindicator3-1, which Bookworm does not provide under that name. GNOME requires an AppIndicator extension for the tray. Windows and WSL scanning has provider-specific limits, so check the documented scan mode for your tools.

At the measured commit, the README described the macOS app as ad-hoc signed and not notarized with an Apple Developer ID, with an Open Anyway procedure for Gatekeeper. That historical documentation does not establish the signing state of a current download.

Issue 720 reports Kaspersky behavior detection and quarantine of tracker.js in v1.1.2 on Windows. The reporter also said TokenTracker.exe was unsigned. Matching a file hash to upstream does not settle a behavior alert or establish either malware or a false positive.

On October 14, the maintainer reported submitting the v1.3.14 Windows installer for Kaspersky reanalysis and said the reported tracker.js hash was shown as Clean on OpenTip. The issue remained open for tracking on October 24. That update does not establish that every installer or behavior alert has been cleared. We did not perform antivirus or signing checks.

The historical v1.1.3 release separately documents Command Code tracking, a Windows desktop quota widget, Linux sign-in fixes, and SHA-256 checksums for six desktop artifacts. Checksums identify artifacts; they do not establish compatibility or safety.

Choosing an interface and a next step

ccusage documents daily, weekly, monthly, and session reports from local coding-agent data, including combined reports across detected sources and JSON output. It is a relevant choice when those terminal reports answer your question.

Tokscale documents an interactive TUI, CLI reporting, web visualization, JSON export, and optional leaderboard submission. Consider it when terminal exploration is your preferred interface. We did not benchmark either alternative against TokenTracker.

TokenTracker's documented dashboard, desktop views, and quota display make it a candidate for personal monitoring. Evaluate the integrations you use, check their permissions and network behavior, and compare a defined period with provider records. Our stored run supplies dependency and test-command evidence, not an end-to-end adoption result.

How the scores work

These are editorial evidence ratings, not benchmark results. The scale is 1 for major documented obstacles, 2 for limited support with important unresolved checks, 3 for a usable documented path with material verification gaps, 4 for detailed support with narrower gaps, and 5 for strong documentation plus direct verification of the relevant behavior. Setup covers reaching a working application; docs covers actionable instructions and caveats; community covers visible maintenance and issue handling; maturity covers verified reliability and compatibility. Unknown adoption and untested platforms do not earn higher scores.

Alternatives

ProjectWhat it isPick it when
ccusageA CLI that turns local coding-agent usage data into daily, weekly, monthly, and session reports.Choose ccusage when terminal reports and JSON output match your workflow. Its own README documents reports combining detected sources as well as source-specific commands.
TokscaleA coding-agent usage tracker with an interactive terminal interface, CLI reports, and web visualization.Choose Tokscale when you want to explore usage in an interactive TUI. Its README also documents JSON export and optional leaderboard submission.

What people are saying

  1. [github-trending] xiufengsun/TokenTracker

Sources

  1. TokenTracker README
  2. TokenTracker v1.1.3 release
  3. OmO double-counting report
  4. Kiro CLI undercount report
  5. Kaspersky false-positive report

More dev tools reviews