Track aider token usage
Counted through burnlog wrap, on whichever provider aider is configured against — including two providers in the same session.
Counting aider in under a minute
- 01Run aider under wrap$ burnlog wrap -- aider
Every provider variable aider might read is pointed at the loopback server at once, so it doesn't matter which one it picks.
- 02Check the numbers$ burnlog me
Your own burn over the last six months, split by model — a read, so it reports without uploading anything.
Multi-provider sessions count correctly
aider is commonly run with a strong model for edits and a cheap one for everything else, sometimes across two providers at once. wrap sets every supported base URL simultaneously, so both sides are counted, each priced at its own model's rate.
Anthropic streaming needs particular care: usage arrives split across two events, with input on message_start and the output total — not a delta — on message_delta. Reading only one of them undercounts every streamed response, which is most of them.
What you get for it
A rank on the public board, a rank ladder from Spark to Supernova, achievements earned from real usage, and a README badge that updates itself.
It's free, the CLI is MIT-licensed, and the whole app self-hosts against your own Postgres if you'd rather keep the board private.
What burnlog can't see
Put aider on the board
One command. It scans, shows you your numbers, and only then asks for an account.