What each tokennations command does. All state lives locally under ~/.tokennations/ - your saved sync token, the per-session totals used to compute deltas, and a local log of every sync run.
View on npmSaves your personal sync token so later commands know who you are. Walks you through signing in on the dashboard and generating a token, then you paste it in here. The CLI itself never does GitHub auth directly. Run this once, before anything else.
Once the token is saved, it also asks whether to turn on automatic syncing every 15 minutes in the background, the same thing schedule below does, just offered inline here. A token alone doesn't sync anything by itself, so this step is what actually starts reporting your usage. Answering no just leaves sync and schedule available to run by hand whenever you're ready.
Reads your local Claude Code, Codex, Gemini CLI, and other supported tools' usage and reports how many new tokens you've earned since the last sync.
Synced 300 new tokens across 2 session(s) (claude, codex). By model — claude-opus-4-5: 300, claude-sonnet-4-5: 0
A session seen for the first time only sets a starting point and reports 0 new tokens. That's expected, not a bug, since nothing before your first sync ever counts. A session whose total went down since last time (log rotation, truncation) is treated as a reset rather than a negative delta. Both are called out in the output when they happen.
Sets up a background job so sync runs automatically every 15 minutes, instead of you having to remember to run it by hand. Picks the right mechanism for your OS: launchd on macOS, a crontab entry on Linux, Task Scheduler on Windows.
Safe to re-run any time, it self-heals rather than erroring if a job already exists. Requires being logged in first.
A read-only snapshot: are you logged in, is auto-sync scheduled and actually running, and what the last sync found.
Logged in — token abcd...1234 Auto-sync: scheduled (loaded) Last sync: 2026-08-25T09:53:34.415Z — 210 new tokens across 3 session(s) (claude)
Removes whatever schedule set up. Only ever touches the one entry it created, never anything else already in your crontab or launchd config.
Safe to run even if nothing was scheduled, it just says so and exits cleanly.
Removes your saved sync token. sync will refuse to run again until you log in again.
Deliberately doesn't stop a scheduled background job, those are separate concerns. Run unschedule too if you want to stop syncing entirely.
Once you're signed in, Settings has the install command and your sync token.