Track Cursor token usage

Counted exactly, subscription included. burnlog reads Cursor's own usage records — the same ones on your Cursor dashboard — using the Cursor login already on your machine.

read from local logs · free · open-source CLI · tokens only

Counting Cursor in under a minute

01
Paste the prompt into your agent
Copy the setup prompt from burnlog.net and paste it into any coding agent. It installs the CLI, shows you your numbers first, and asks before anything is uploaded.
02
Or run it yourself
```
$ npx @sxnalabs/burnlog
```
burnlog finds every agent on the machine, reads its usage, and offers GitHub sign-in.
03
Keep it current
```
$ burnlog install
```
Installs a hook so future sessions sync themselves.

Where the numbers come from

Cursor's included models run on Cursor's servers, so the token accounting was never on your disk. It is on Cursor's usage dashboard, per request: model, input, output, cache reads and writes. That is the only honest source for those tokens, so it is the one burnlog reads.

The CLI takes the login Cursor already stored on your machine, asks cursor.com for your usage events, and turns each one into a count. The login is sent only to cursor.com. burnlog never stores it, logs it, or uploads it — only the token counts go to burnlog.

Your own API key works too

If you point Cursor at your own provider key, those calls show up in Cursor's usage records as well. For anything outside Cursor on your own key, burnlog wrap counts at the wire across 14 providers without installing a certificate or decrypting anything.

What burnlog can't see

Cursor has to be signed in on the machine that syncs. If its saved login has expired, open Cursor once and sync again.
Team seats report personal usage; usage attributed only to a team may not appear.

Put Cursor on the board

One command. It scans, shows you your numbers, and only then asks for an account.

$ npx @sxnalabs/burnlog

See the leaderboard →

Other agents

Claude Code · Codex · Gemini CLI · aider · opencode