Doesn't work at all. Antigravity's Gemini, Zed with Opencode model.

[pegasusearl]

I ran tokentracker then do some AI coding.
I am using Antigravity IDE with gemini and Zed editor with opencode's Big Pickle free model.
But after I used them, the tokentracker doesn't track anything at all. Still zero.

Also can we not automatically open tokentracker link everytime we launch tokentracker? It's quite annoying when running the script at startup. Or do I not actually do that? Do I have to have tokentracker running when using AI?

❯ tokentracker-cli.cmd
First time? Setting up Token Tracker...

████████╗ ██████╗ ██╗  ██╗███████╗███╗   ██╗
╚══██╔══╝██╔═══██╗██║ ██╔╝██╔════╝████╗  ██║
   ██║   ██║   ██║█████╔╝ █████╗  ██╔██╗ ██║
   ██║   ██║   ██║██╔═██╗ ██╔══╝  ██║╚██╗██║
   ██║   ╚██████╔╝██║  ██╗███████╗██║ ╚████║
   ╚═╝    ╚═════╝ ╚═╝  ╚═╝╚══════╝╚═╝  ╚═══╝
      ████████╗██████╗  █████╗  ██████╗██╗  ██╗███████╗██████╗
      ╚══██╔══╝██╔══██╗██╔══██╗██╔════╝██║ ██╔╝██╔════╝██╔══██╗
         ██║   ██████╔╝███████║██║     █████╔╝ █████╗  ██████╔╝
         ██║   ██╔══██╗██╔══██║██║     ██╔═██╗ ██╔══╝  ██╔══██╗
         ██║   ██║  ██║██║  ██║╚██████╗██║  ██╗███████╗██║  ██║
         ╚═╝   ╚═╝  ╚═╝╚═╝  ╚═╝ ╚═════╝╚═╝  ╚═╝╚══════╝╚═╝  ╚═╝

Token Tracker  Local-first usage across 16 AI CLIs
----------------------------------------------
Nothing leaves your machine — token counts only, never prompts or responses.
----------------------------------------------

  Tracks: Claude Code, Codex CLI, Cursor, Gemini CLI, OpenCode +11 more
  Dashboard: http://localhost:7680
Local configuration complete.

Integration Status:
  o Codex CLI              [Skipped - Config not found]
  o Claude                 [Skipped - Config not found]
  * Gemini                 [Hooks installed]
  * Opencode Plugin        [Plugin installed]
  o Cursor                 [Skipped - Not installed]
  o CodeBuddy              [Skipped - Config not found]
  o OpenClaw Session Plugin [Skipped - OpenClaw CLI not found]
  o Every Code             [Skipped - Config not found]

Setup complete!

  No usage history yet — run any AI CLI and tokens appear within a minute.

  Dashboard: http://localhost:7680

  ⭐ Star us if useful: https://github.com/mm7894215/TokenTracker
Syncing local data...
(node:13652) ExperimentalWarning: SQLite is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Sync warning: os is not defined

  tokentracker dashboard running at:

    http://127.0.0.1:7680

  Data: C:\Users\komi\.tokentracker\tracker\queue.jsonl
  Press Ctrl+C to stop.

Shutting down...

[krotname]

The Sync warning: os is not defined line is the first thing I would chase. If sync aborts there, the dashboard can stay at zero even if the integrations were installed.

A couple of notes from the current CLI behavior:

• Antigravity and Zed are not hook installs in the same sense as Gemini CLI. They are passive readers. Antigravity is read from ~/.gemini/antigravity*/brain/**/transcript.jsonl; Zed is read from the Zed threads.db database. So after using those tools, you need a successful tokentracker sync / startup sync for the rows to appear.
• Zed should include bring-your-own providers too, as long as the thread has token usage in its thread JSON. It is not limited to hosted Zed models.
• To avoid opening the browser on startup, run:

tokentracker serve --no-open

or, if you only want to parse local data and not keep the dashboard server running:

tokentracker sync --debug

For this specific case I would run tokentracker sync --debug first. If it still prints os is not defined, the useful bug report is the stack trace from that command plus your TokenTracker version. Without the full stack trace it is hard to tell which provider parser is throwing, because the top-level serve command only prints the short Sync warning message.

You do not need TokenTracker running for Antigravity/Zed to create their own local history, but you do need a later sync run to import that history into queue.jsonl.

[pegasusearl]

This is the output.

❯ tokentracker sync --debug
(node:19252) ExperimentalWarning: SQLite is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
ReferenceError: os is not defined
    at resolveDroidSessionsDirs (C:\Users\komi\scoop\persist\nodejs\bin\node_modules\tokentracker-cli\src\lib\rollout.js:5702:28)
    at listDroidSettingsFiles (C:\Users\komi\scoop\persist\nodejs\bin\node_modules\tokentracker-cli\src\lib\rollout.js:5711:16)
    at cmdSync (C:\Users\komi\scoop\persist\nodejs\bin\node_modules\tokentracker-cli\src\commands\sync.js:462:32)
    at async run (C:\Users\komi\scoop\persist\nodejs\bin\node_modules\tokentracker-cli\src\cli.js:33:7)

[mm7894215]

Thanks for the full stack trace — that pinpoints it.

Root cause: the ReferenceError: os is not defined comes from the Droid path resolver, which runs before the Antigravity/Zed/Gemini parsers in a sync pass. That throw aborts the entire sync, so none of your providers get imported — which is why everything stayed at zero even though you only use Antigravity and Zed. The Sync warning: os is not defined line under serve is the same crash.

It's already fixed. This was a bug in an older build, patched in v0.26.1; the current release (v0.55.0) doesn't have it. Please upgrade:

npm i -g tokentracker-cli@latest

Then run tokentracker sync once. Antigravity and Zed are read passively from their own local stores, so a successful sync will import that history into queue.jsonl and the dashboard will populate.

On the browser pop-up: run tokentracker serve --no-open to keep the dashboard server without auto-opening the tab, or just tokentracker sync if you only want to parse local data without running the server. You don't need TokenTracker running while you code — the AI tools write their own local history; you only need a later sync to import it.

[pegasusearl]

Ah thanks. It seems to fix Zed. Although it doesn't catch which project is it's belong to. All usage just said it come from Zed. Good enough for me. Or maybe I misunderstand something.

As for antigravity, it seems it didn't detect it at all. I wonder if it's because I'm still using old Antigravity? I downgraded it because google renamed it to antigravity-ide and messed up my config and chat history. If that's the cause I guess I will have finally painfully to migrate to newer version, or just not track Antigravity token usage. Yes it is. It seems like they finally have migration script for config (but not conversation).