---
{"title": "ccusage vs OpenUsage in 2026: What Each Tracks for Developers", "description": "Compare ccusage and OpenUsage on what each reports, what each costs and what to check before you pick one for tracking your AI coding usage.", "url": "https://supakeeper.com/ccusage-vs-openusage/", "date": "2026-11-10"}
---
Compare ccusage and OpenUsage on what each reports, what each costs and what to check before you pick one for tracking your AI coding usage.

ccusage exports usage data as structured JSON, and it can track usage within Claude's billing windows [^1] [^1]. OpenUsage tracks spending, quotas and rate limits across AI coding tools [^2], and Codex Forecast estimates when Codex usage limits reset [^3].

| Option | What its sources say it does | Cost | Account or install |
|---|---|---|---|
| ccusage | It analyzes token usage and costs from coding agent command-line tools, using local data [^1]. It exports data in structured JSON format [^1]. It tracks usage within Claude's billing windows, with active block monitoring [^1]. | not published | Can be run without a global installation [^1]. |
| OpenUsage | It tracks spending, quotas and rate limits across AI coding tools [^2]. It is open source and runs locally [^2]. It shows remaining credits, reset windows and rate limits where providers expose them [^2]. | not published | It runs locally, and its dashboard runs on your machine [^2]. |
| Codex Forecast | It estimates when OpenAI will next reset Codex usage limits [^3]. It combines an account it checks every 60 seconds, OpenAI staff announcements and the OpenAI status page [^3]. Each reset used in the forecast is listed with a link to where it was announced [^3]. | Free [^3] | No account [^3]. A website with a public API [^3]. |

## The short answer

ccusage can export its data as structured JSON, a plain text format that other programs can read [^1]. It can also track usage within Claude's billing windows, with active monitoring of 5-hour blocks [^1]. OpenUsage tracks spending, quotas and rate limits across AI coding tools, and it can show that usage in your terminal status bar [^2] [^2]. Codex Forecast answers a different question, namely when Codex usage limits reset [^3]. If you want usage data in a file your own scripts can read, ccusage's sources say it exports structured JSON [^1]. If you want usage visible while you work in a terminal, OpenUsage's sources say it shows that in the status bar [^2].

## What ccusage and OpenUsage are built for

ccusage's page says it can export data in structured JSON format [^1], and it describes tracking usage within Claude's billing windows with active block monitoring [^1]. It lists its license as MIT [^1]. OpenUsage's page describes tracking spending, quotas and rate limits across the AI coding tools you use [^2]. It says the active tool's usage can appear in a tmux status bar, which is a terminal tool that splits one window into panes, and in the status line of Claude Code [^2]. It says it supports 34 providers, and counting [^2]. The facts used here describe these features and say nothing more about how either tool is built, so check each tool's own pages for detail.

## 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 [^3]. By its own description, the estimate combines an account it checks every 60 seconds, OpenAI staff announcements and the OpenAI status page [^3]. When a measured refill and an announcement disagree, it trusts the measured refill [^3]. Each reset used in the forecast is listed with a link to where it was announced [^3]. Its named-day predictions are scored in public, misses included [^3]. It is an independent tracker, and it is not affiliated with OpenAI [^3]. A public API that needs no key gives stats, reset history split into pages, forecasts and operational health [^3]. The API has a published OpenAPI specification, a standard format for describing an API's requests [^3].

## Pricing and fees

Codex Forecast is free, with no account [^3]. Its public API needs no key [^3]. The facts used here do not state a price for ccusage, so no cost is published here. The facts used here do not state a price for OpenUsage either, so no cost is published here, although its page does describe tracking spending [^2]. ccusage's page lists its license as MIT [^1]. Check each tool's own pages before you assume anything about its cost.

## Setting it up and daily use

Codex Forecast is a website with a public API, so you can open it in a browser or call its API from your own code [^3]. The site and API share a snapshot that is cached for up to five minutes, so the figures you see can be up to five minutes old [^3]. A published OpenAPI specification describes the API's requests in a standard format [^3]. You can opt in to free emails that are sent when a reset actually happens [^3]. OpenUsage can show usage in your tmux status bar and in the status line of Claude Code [^2]. For ccusage, the facts used here describe a 5-hour view of usage within Claude's billing windows [^1], and they do not describe installation steps, so check its own page for setup. The facts used here say nothing more about daily use for either tool.

## Things to check before you choose

Start with the question you need answered. Codex Forecast estimates when Codex usage limits reset [^3], while the facts used here for ccusage and OpenUsage describe usage data, spending and quotas. If reset timing is your question, check the tools' own pages. Ask whether you need the data in a file for your own scripts, since ccusage's page describes structured JSON output [^1]. Ask which AI tools you use, and check whether they are among the providers OpenUsage supports [^2]. Ask where your data goes. Codex Forecast shares a snapshot cached for up to five minutes [^3], and its public API needs no key [^3]. Ask about cost against your own budget. Codex Forecast is free [^3], and the facts used here give no price for ccusage or OpenUsage, so check their pages.

## How to choose

If you want usage data in structured JSON for your own scripts, ccusage's page describes that output [^1]. If you want to track usage within Claude's billing windows, ccusage's page describes that too [^1]. If you want spending, quotas and rate limits tracked across AI coding tools, OpenUsage's page describes that [^2], and it says it supports 34 providers [^2]. If you want usage visible in your terminal status bar, OpenUsage's page describes that as well [^2]. If you want to know when Codex usage limits reset, Codex Forecast estimates that [^3], and it can email you when a reset happens if you opt in [^3].

## Frequently asked questions

### Is Codex Forecast free to use?

Codex Forecast is free, with no account [^3]. It is a website with a public API, and that API needs no key [^3]. The public API gives stats, reset history split into pages, forecasts and operational health [^3]. You can opt in to free emails that are sent when a reset actually happens [^3].

### Does ccusage export its usage data as JSON?

Yes. ccusage's page says it can export data in structured JSON format [^1]. Structured JSON is a plain text format that other programs can read, which makes it useful if you want to feed usage numbers into your own scripts. The facts used here give no further detail about the fields in the file, so check the tool's own documentation for those.

### Can OpenUsage show usage in a terminal status bar?

Yes. OpenUsage's page says it can show the active tool's usage in a tmux status bar and in the status line of Claude Code [^2]. Tmux is a terminal tool that splits one window into panes, so the usage line appears where you already work. The same page says OpenUsage tracks spending, quotas and rate limits across AI coding tools [^2].

### Can Codex Forecast tell when Codex usage limits reset?

Codex Forecast estimates when OpenAI will next reset Codex usage limits [^3]. By its own description, the estimate combines an account it checks every 60 seconds, OpenAI staff announcements and the OpenAI status page [^3]. It lists each reset used in the forecast with a link to where it was announced [^3]. Treat the result as an estimate, and check the listed sources if the timing matters to you.

### What license does ccusage use?

ccusage's page lists its license as MIT [^1]. A license name alone does not tell you every term that applies, so read the full license text before you reuse the code in your own work.

It is free, with no account and no paid tier. [^3] - [Visit Codex Forecast](/go/start-codexforecast)

## Sources

[^1]: ccusage, github.com/ryoppippi/ccusage, read 2026-11-07 (https://github.com/ryoppippi/ccusage)
[^2]: OpenUsage, openusage.sh, read 2026-11-07 (https://openusage.sh)
[^3]: Codex Forecast's own description of itself (the product of this site's publisher) (/go/start-codexforecast)
