OpenCode usage monitor: three ways to watch your tokens, ranked

If you want an OpenCode usage monitor that keeps watching while you code, install UsageAtlas: it is free, open source, and reads OpenCode's local database into a desktop dashboard with daily totals and history. For a one-off look, OpenCode's built-in stats command does the job, and your provider consoles remain the place to confirm what you were charged.

Below are the three realistic options, ranked for someone who uses OpenCode most days.

1. UsageAtlas: a desktop monitor for OpenCode and the rest

UsageAtlas is a local-first desktop app for AI coding usage. For OpenCode it picks up the tokens, requests, models and sessions that OpenCode stores on the same computer, with no extra login.

What makes it a monitor rather than a report:

• It stays open, so today's numbers are there whenever you glance at it.
• The History view keeps day-by-day records, which makes a sudden spike easy to see.
• Insights break usage down by model and by time of day and weekday.
• A filter shows OpenCode alone, or you can see it next to Claude Code, Codex, Cursor and other supported tools.

Cost appears as an estimate based on token counts and model prices, unless OpenCode itself reports a figure. It runs on Windows, macOS and Linux, needs no account for local tracking, and does not read your prompts or responses.

Best for: anyone who runs OpenCode daily, or switches between OpenCode and other coding agents.

2. opencode stats: the built-in check

OpenCode ships a stats command. Its documentation says it prints token usage and cost statistics for your sessions. A few flags make it more useful:

• --days 7 limits the output to the last week.
• --models adds a breakdown by model, or the top few if you pass a number.
• --project filters to one project, and an empty string means the current one.

Best for: a quick answer in the terminal. It is a snapshot, so you have to remember to run it, and it covers OpenCode only.

3. Provider consoles: the billing truth

OpenCode sends requests to whichever providers you configure. Each of those providers has its own usage and billing page, and that page is the final word on money.

Best for: checking an invoice. The catch is that you need one tab per provider, and none of them knows which requests came from OpenCode and which came from other apps sharing the same key.

Side by side

Which one to pick

Start with UsageAtlas as the everyday monitor, because it is the only option of the three that keeps a running picture without you asking for it. Use opencode stats when you are already in the terminal and want a single number. Open the provider consoles at the end of the month to settle the bill.

One honest caveat: OpenCode's local data does not include provider rate limits or quotas, so no local monitor can warn you before a provider cuts you off. What it can tell you is how fast you are using tokens, which is usually the earlier signal.

Getting started

Download UsageAtlas from its home page, open it on the computer where you run OpenCode, and filter to OpenCode. The OpenCode usage tracker guide on the UsageAtlas site walks through the same setup and links to the cost and Windows notes.