ccusage vs OpenAI Usage Dashboard in 2026

ccusage and OpenAI Usage Dashboard compared on what each does, what each costs and what to check before you pick one to track your coding agent token usage.

By SupaKeeper · 2026-10-16

SupaKeeper is published by LunarWerx, which makes some of the tools compared here.

ccusage analyzes coding agent CLI token usage and costs from local data, and the OpenAI Usage Dashboard is not described in the given sources. Codex Forecast estimates when Codex usage limits reset. Each tool answers a different question for a developer.

Option	What its sources say it does	Cost	Account or install
ccusage	Analyzes coding agent CLI token usage and costs from local data ^[1]; turns it into daily, weekly, monthly, and session reports ^[1]; supports sources including Claude Code, Codex, OpenCode, Amp, Droid, Codebuff, Hermes Agent, pi-agent, Goose, OpenClaw, Kilo, Kimi, Qwen, GitHub Copilot CLI, Gemini CLI, Antigravity, Grok Build CLI, and ZCode ^[1]	not published	can be run directly without a global installation using npx ^[1]
OpenAI Usage Dashboard	not described in the sources given	not published	not published
Codex Forecast	Its own description says it estimates when OpenAI resets Codex usage limits ^[2]; it combines several sources ^[2]; it can email you when a reset happens, if you opt in ^[2]	free, no paid tier ^[2]	no account ^[2]; a website with a public API ^[2]

The short answer

A developer who tracks token usage and costs for coding agent command-line tools has at least two options to look at. ccusage analyzes coding agent CLI token usage and costs from local data ^[1]. The OpenAI Usage Dashboard is not described in the given sources on this page. Codex Forecast estimates when OpenAI will next reset Codex usage limits ^[2]. Pick by the question you have: the question of how much you spent on coding agent CLIs points to ccusage, the question of your OpenAI platform usage points to the OpenAI Usage Dashboard, and the question of when a Codex reset is due points to Codex Forecast.

What ccusage, OpenAI Usage Dashboard is built for

ccusage analyzes coding agent CLI token usage and costs from local data ^[1]. It reads local usage data from coding agent CLIs and turns it into daily, weekly, monthly, and session reports ^[1]. It offers a 5-hour blocks report that tracks usage within Claude's billing windows with active block monitoring ^[1]. It tracks and displays cache creation and cache read tokens separately ^[1]. It has an offline mode that uses pre-cached pricing data without network connectivity ^[1]. It allows overriding token pricing per raw model name in ccusage.json without rebuilding ^[1]. It is licensed under MIT ^[1]. The OpenAI Usage Dashboard is not described in the sources given on this page.

What Codex Forecast is built for

Codex Forecast is made by the team that publishes this site. The product describes its method as a statistical estimate of when OpenAI will next reset Codex usage limits ^[2]. By its own description, the estimate combines an account it checks every 60 seconds, OpenAI staff announcements and the OpenAI status page ^[2]. The product describes listing each reset used in the forecast with a link to where it was announced ^[2]. The product describes emails you can opt in to, sent when a reset actually happens ^[2]. The product describes a public API that needs no key, giving stats, paginated reset history, forecasts and operational health ^[2]. It describes a published OpenAPI specification for the API ^[2]. It describes the site and API as sharing a snapshot cached for up to five minutes ^[2]. It describes itself as a website with a public API ^[2]. It describes itself as an independent tracker, not affiliated with OpenAI ^[2].

Pricing and fees

Codex Forecast is free, with no account and no paid tier ^[2]. The facts given here do not state a dollar price for ccusage, which is licensed under MIT ^[1], and its page mentions running it without a global install ^[1], but gives no fee. If you need the cost of ccusage or the OpenAI Usage Dashboard for your own use, check their own pages.

Setting it up and daily use

ccusage can be run directly without a global installation using npx ^[1]. It reads local usage data from coding agent CLIs and turns it into daily, weekly, monthly, and session reports ^[1]. It can output reports in structured JSON format with the --json flag ^[1]. It can hide cost columns and JSON cost fields with --no-cost ^[1]. It has an offline mode that uses pre-cached pricing data without network connectivity ^[1]. Codex Forecast is a website with a public API, so you open it in a browser or call its API for data ^[2]. The site and API share a snapshot that is cached for up to five minutes ^[2]. There is no account and no paid tier to set up ^[2]. You can opt in to free emails sent when a reset actually happens ^[2]. Setting up and using the OpenAI Usage Dashboard is not described in the sources on this page, so check its own pages for anything further.

Things to check before you choose

Ask what you need the tool to tell you. ccusage analyzes coding agent CLI token usage and costs from local data ^[1], while Codex Forecast predicts when Codex usage limits reset ^[2]. Ask whether you want to track usage within Claude's billing windows, since ccusage offers a 5-hour blocks report for that ^[1]. Check data that leaves your machine. Codex Forecast shares a snapshot cached for up to five minutes ^[2], and its public API needs no key ^[2]. Check whether either tool charges for use; Codex Forecast is free ^[2], and no price is published for ccusage or the OpenAI Usage Dashboard.

How to choose

The three tools answer different questions for a developer. If the question is how many tokens a coding agent CLI used and what it cost, ccusage reads local usage data and turns it into reports ^[1]. If the question is when OpenAI will next reset Codex usage limits, Codex Forecast is built for that ^[2], and it can email you when a reset happens if you opt in ^[2]. The OpenAI Usage Dashboard is not described in the sources given here, so nothing is stated on this page about what it does. If you need a public API that gives stats and reset history without a key, Codex Forecast offers one ^[2]. If you need JSON output from your usage reports, ccusage can produce that ^[1].

Frequently asked questions

Is ccusage free to use?

The facts given here do not state a dollar price for ccusage, which is licensed under MIT ^[1], and its page says you can run it directly without a global installation ^[1]. Check its own pages if you need to confirm whether any cost applies to your use.

Does the OpenAI Usage Dashboard cost anything?

The OpenAI Usage Dashboard is not described in the given sources, and no fee for using it is published. Check its own pages if you need the cost.

Can ccusage track usage for multiple coding agent CLIs?

Yes. ccusage reads local usage data from coding agent CLIs and turns it into daily, weekly, monthly, and session reports ^[1]. The full list of the command-line tools it supports is shown in the table on this page. It is licensed under MIT ^[1], and it can be run directly without a global installation ^[1].

Can Codex Forecast tell when Codex usage limits reset?

Yes, Codex Forecast estimates when OpenAI will next reset Codex usage limits ^[2]. By its own description, the estimate combines an account it checks every 60 seconds, OpenAI staff announcements and the OpenAI status page ^[2]. It can email you when a reset actually happens if you opt in ^[2].

Can ccusage output data in JSON format?

Yes, ccusage can output reports in structured JSON format with the --json flag ^[1]. It can also hide cost columns and JSON cost fields with --no-cost ^[1]. It has an offline mode that uses pre-cached pricing data without network connectivity ^[1].

It is free, with no account and no paid tier. ^[2]

Try Codex Forecast