oc-lens: see where your opencode tokens really go
Local, read-only analytics for your opencode history. Run `npx oc-lens` and it finds your opencode database, opens a dashboard in your browser, and never writes a byte to your history. It answers three questions: • Where did the agent loop? The same failing command run four times, the same file re-read for nothing. Repeats are matched on tool and input, so ordinary work isn't flagged. • What did my provider cost me? Rate limits, outages, broken streams, the retries opencode hides inside a step, and the cache price you lose when a call is resent. • Where do the tokens go? By day, model, project, agent and session, priced with your own rates. If a model isn't priced, it says "not priced", never $0.00. Also: full session replay with failures and loops marked in place, activity heatmaps, tool rankings, and JSON/ZIP export. MIT licensed, 100% local.
More from members
All projectsSee what other members are building and what each project is looking for.
Comments · 0