Track Cursor token usage
Depends entirely on whose key you're spending. Your own API key, counted exactly. Cursor's included subscription, not countable by anything on your machine — and any tracker claiming otherwise is guessing.
Counting Cursor in under a minute
- 01Point Cursor at your own API key
In Cursor's settings, supply your own provider key and override the base URL. This is the mode where the requests leave your machine on a path you control.
- 02Start the burnlog proxy$ burnlog wrap -- <your command>
wrap runs a loopback server, sets the standard base-URL variables at it, forwards upstream over ordinary HTTPS, and reads the usage field off each response.
- 03Sync
Events land in ~/.burnlog/events first, so counting keeps working with no network and no account, and upload when you next sync.
Why the subscription case is impossible, for everyone
When you use Cursor's included models, Cursor's servers call the provider with Cursor's key. Your machine sends a request to Cursor and gets an answer back; the token accounting happens somewhere you have no access to. No local tool can count those tokens, because the numbers were never on your computer to begin with.
Cursor's own dashboard is the only honest source for that spend. If a tracker shows you a confident Cursor number while you're on the subscription, it is inferring it — usually by counting characters and dividing — and that estimate will not match your bill.
burnlog would rather show you nothing than show you a number it made up.
The part that does work
Run Cursor against your own key and every call becomes countable, exactly, from the provider's own usage field — the same number the provider will bill you for. That covers 14 providers: Anthropic, OpenAI, Google, Mistral, Cohere, OpenRouter, Groq, xAI, DeepSeek, Together, Fireworks, Perplexity, Cerebras, and Ollama.
wrap is deliberately not a man-in-the-middle proxy. It installs no certificate authority and decrypts nothing — it sets the base-URL environment variables the SDKs already read and forwards over normal HTTPS. Nothing about your machine's trust store changes.
What burnlog can't see
Put Cursor on the board
One command. It scans, shows you your numbers, and only then asks for an account.