All UsageAtlas guides

OpenCode usage tracker

OpenCode usage tracker for tokens, models, and sessions

Track OpenCode usage locally: tokens, requests, models, sessions, and estimated cost, then see it beside Codex, Claude, and Cursor.

Quick answer

UsageAtlas tracks OpenCode usage from the local database: tokens, requests, models, sessions, and estimated cost. You can see OpenCode alone or beside Codex, Claude, and Cursor. Nothing is sent to a UsageAtlas server.

Download app to track this on your machine

See OpenCode usage on this machine

OpenCode already stores tokens, requests, models, and sessions locally. An OpenCode usage tracker is useful when you want a dashboard instead of digging through session files.

UsageAtlas reads that database and shows the same picture it uses for other sources. Step-by-step: how to see OpenCode usage.

OpenCode usage dashboard, plus cost

Today, History, and Insights work for OpenCode the same way they work for Codex. Track token usage, filter to OpenCode, or leave the other tools in.

OpenCode often sits in front of several model providers, so a single invoice is a poor map. OpenCode cost tracking covers how estimates are labeled.

Questions, answered

Can UsageAtlas track OpenCode token usage?

Yes. Local tokens, requests, models, and sessions, in the same dashboard as your other supported tools.

Does it show an OpenCode usage dashboard?

Yes. That is the desktop app, with a filter for OpenCode only.

Is OpenCode data sent off the machine?

Usage is processed locally. If you sign in for optional free cloud save, usage summaries are uploaded to your account. Prompts, responses, and project and session details are not included.