Track Kilo Code CLI Token Usage & Costs
SuperBased reads the Kilo Code CLI's SQLite store at ~/.local/share/kilo/kilo.db - the same path on Linux, macOS, and Windows. Track Kilo Code CLI token usage.SuperBased tracks Kilo Code CLI token usage and cost on your own machine. SuperBased reads the Kilo Code CLI's SQLite store at ~/.local/share/kilo/kilo.db - the same path on Linux, macOS, and Windows. Per-message tokens are net; kilo-auto/* gateway models resolve through explicit pricing aliases. No account, no telemetry, no data leaves your laptop - SuperBased is a single open-source binary that also covers 39 other AI coding tools.
How SuperBased captures Kilo Code CLI
- Where the data lives - SuperBased reads Kilo Code CLI's sessions from
~/.local/share/kilo/kilo.db- the same path on Linux, macOS, and Windows. - Capture tactic - Per-message tokens are net of cache;
kilo-auto/*gateway models resolve through explicit pricing aliases. - Token accuracy: From local logs - SuperBased reads token counts from Kilo Code CLI's own local session files - the counts the tool itself recorded. Kilo Code CLI talks only to its own backend, so there's no proxy route for exact provider-side counts.
- Proxy routing - Kilo Code CLI talks only to its own backend with no base-URL knob, so there is no proxy route - capture stays on the local files above.
2-minute quickstart
Install SuperBased and start the local daemon (it auto-registers hooks for every AI tool it detects):
npm install -g @superbased/observer # or: pip install superbased-observer
observer start
That's it - keep using Kilo Code CLI exactly as you do now. SuperBased's watcher captures every session automatically.
Verify capture at any time:
observer doctor kilo-code-cli
What you'll see
- Cost breakdown - per-session and per-day spend for Kilo Code CLI, priced from SuperBased's built-in model pricing table.
- Session history - every Kilo Code CLI session with its model, duration, and token totals, searchable on the local dashboard.
- Local dashboard - everything is viewable at
http://localhost:8080; nothing is uploaded.
Limitations for Kilo Code CLI
- Kilo Code CLI talks only to its own backend (no custom base-URL), so token accuracy is limited to what it logs locally - there is no proxy route for exact provider-side counts.
- Counts come from Kilo Code CLI's own logs, so they are the tool's self-reported totals - accurate to what Kilo Code CLI recorded, but not provider-verified unless you route through the proxy.
- SuperBased captures on write, so an in-progress Kilo Code CLI session appears only once the tool next flushes it to disk.
- Conversation compression is off by default; token and cost tracking work without it.
FAQ
Is my Kilo Code CLI data sent anywhere?
No. SuperBased runs entirely on your machine - it reads Kilo Code CLI's local session files (and, if you opt in, proxies your API traffic through localhost). Nothing is uploaded, there is no account, and there is no telemetry.
How accurate are the token counts?
SuperBased reads token counts from Kilo Code CLI's own local session files - the counts the tool itself recorded. Kilo Code CLI talks only to its own backend, so there's no proxy route for exact provider-side counts.
Do I have to change how I run Kilo Code CLI?
No. Run observer start once and keep using Kilo Code CLI as usual - SuperBased captures every session automatically.
Does it track cache and reasoning tokens?
SuperBased captures whatever Kilo Code CLI records locally, and prices it with the built-in pricing table.
Where does SuperBased read Kilo Code CLI data from?
SuperBased reads Kilo Code CLI's sessions from ~/.local/share/kilo/kilo.db - the same path on Linux, macOS, and Windows - all on your own machine. Kilo Code CLI talks only to its own backend with no base-URL knob, so there is no proxy route - capture stays on the local files above.