Track Qoder Token Usage & Costs
SuperBased records Qoder sessions and actions from its Claude-Code-shaped JSONL, but Qoder keeps token usage server-side only. Track Qoder token usage locally.SuperBased tracks Qoder token usage and cost on your own machine. SuperBased records Qoder sessions and actions from its Claude-Code-shaped JSONL, but Qoder keeps token usage server-side only: local logs carry no token counts or model, so SuperBased shows session history without a local cost total. 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 Qoder
- Where the data lives - SuperBased reads Qoder's sessions from Claude-Code-shaped JSONL under
~/.qoder/projects/. - Capture tactic - The local logs carry no token counts or model - Qoder keeps usage server-side - so SuperBased records session and action history without a local cost total.
- Token accuracy: Session metadata only - Qoder keeps token usage on its own servers and writes no counts locally, so SuperBased records the session and its actions but cannot show a local token total.
- Proxy routing - Qoder talks only to its own backend with no base-URL knob, so there is no proxy route - capture stays on the local files above.
- Hooks - SuperBased registers into Qoder's own hook system, so sessions are captured as they happen.
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 Qoder exactly as you do now. SuperBased's watcher captures every session automatically.
Verify capture at any time:
observer doctor qoder
What you'll see
- Session & action history - every Qoder session with its model, duration, and tool calls; token usage stays on Qoder's servers, so there is no local cost total.
- Local dashboard - everything is viewable at
http://localhost:8080; nothing is uploaded.
Limitations for Qoder
- Qoder reports usage only on its own servers, so SuperBased cannot show a local token or cost total - you still get full session and action history.
- Known token-capture gap: usage server-side only - local logs carry zero tokens and no model; no base-URL knob.
- Qoder 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.
- Conversation compression is off by default; token and cost tracking work without it.
FAQ
Is my Qoder data sent anywhere?
No. SuperBased runs entirely on your machine - it reads Qoder'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?
Qoder keeps token usage on its own servers and writes no counts locally, so SuperBased records the session and its actions but cannot show a local token total.
Do I have to change how I run Qoder?
No. Run observer start once and keep using Qoder as usual - SuperBased captures every session automatically.
Does it track cache and reasoning tokens?
SuperBased captures whatever Qoder records locally. Note one honest gap: usage server-side only - local logs carry zero tokens and no model; no base-URL knob.
Where does SuperBased read Qoder data from?
SuperBased reads Qoder's sessions from Claude-Code-shaped JSONL under ~/.qoder/projects/ - all on your own machine. Qoder talks only to its own backend with no base-URL knob, so there is no proxy route - capture stays on the local files above.
Why don't I see token costs for Qoder?
Qoder keeps usage on its own servers and writes no token counts to disk, so SuperBased shows session and action history without a local cost total. Everything else - models, timings, tool calls - is still captured.