SupaKeeper Plain comparisons of AI coding tools

ccusage vs Usages in 2026: Usage Tracker Comparison

Compares ccusage, Usages and Codex Forecast on what each does, what each costs and what to check before you pick a usage tracker.

By SupaKeeper ยท

SupaKeeper is published by LunarWerx, the makers of AgentHydra, Copilot AI Productivity Suite, Codex Forecast and Model Odds, which are compared here alongside other tools.

This page compares two usage trackers and one reset forecast, so the right pick depends on what you need to know.

OptionWhat its sources say it doesCostAccount or install
ccusageAnalyzes coding agent command-line token usage and costs from local data [1]. Exports structured JSON with --json [1]. Its page describes a 5-hour blocks report that tracks usage within Claude's billing windows with active block monitoring [1]. Works offline with pre-cached pricing data [1].Not published. Its cost columns can be removed with --no-cost [1].Can be run without a global installation [1]. Licensed under MIT [1].
UsagesAn iPhone app for monitoring AI usage limits [2]. A Mac version is offered [2]. Supports Claude Code, OpenAI Codex, Cursor, GitHub Copilot, GLM, OpenRouter, Grok and Kimi [2]. Usage monitoring across eight providers [2]. Daily, by model and by hour views [2]. Alerts for early forecast, 75% used, 90% used and window reset [2].Not published.An iPhone app, with a Mac version offered [2] [2]. Stores keys in the iPhone Keychain [2]. Credentials never leave the iPhone [2]. Stores history on the device [2].
Codex ForecastGives a statistical estimate of when OpenAI will next reset Codex usage limits [3]. Combines an account checked every 60 seconds, OpenAI staff announcements and the OpenAI status page [3]. Offers opt-in email alerts when a reset happens [3]. A public API gives stats, paginated reset history, forecasts and operational health [3].Free, with no paid tier [3].No account [3]. A website with a public API [3].

The short answer

ccusage analyzes token usage and costs for coding agent command-line tools, working from local data [1]. Usages is an iPhone app for monitoring AI usage limits [2]. Codex Forecast estimates when Codex usage limits reset [3]. Choose by the question you have: a report of coding agent costs from your own machine points to ccusage [1], a glance at usage limits from an iPhone points to Usages [2], and a question about when Codex limits reset points to Codex Forecast [3].

What ccusage and Usages are built for

ccusage analyzes token usage and costs for coding agent command-line tools, working from local data [1]. It tracks and displays cache creation and cache read tokens separately [1]. Its cost columns and JSON cost fields can be removed with --no-cost [1]. Usages is an iPhone app for monitoring AI usage limits [2]. It also offers a Mac version [2]. Its page describes a feature that pauses before opening selected social media apps, with Instagram as the example [2].

What Codex Forecast is built for

Codex Forecast is made by the team that publishes this site. It gives a statistical estimate of when OpenAI will next reset Codex usage limits [3]. 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]. You can opt in to free emails sent when a reset actually happens [3]. A public API that needs no key gives stats, paginated reset history, forecasts and operational health [3]. The API has a published OpenAPI specification [3]. The site and API share a snapshot cached for up to five minutes [3]. It is an independent tracker and is not affiliated with OpenAI [3].

Pricing and fees

Codex Forecast is free, with no account [3]. The facts here do not state a price for ccusage, so its cost is not published here. The facts here do not state a price for Usages either, so its cost is not published here. The only price claim for Codex Forecast is that it is free [3]. A fair comparison of fees needs each tool's price stated in the same way, and the facts here give that only for Codex Forecast. For ccusage, the facts describe a switch that removes cost columns from its output, which is a display setting and not a price [1]. Check each tool's own page for any charge, trial or discount before you rely on it.

Setting it up and daily use

ccusage works from local data [1], and it shows cache creation and cache read tokens separately in its reports [1]. The facts here say nothing more about installing ccusage, so check its page for setup steps. Usages is an iPhone app [2] and it also has a Mac version [2]. The facts here say nothing about how to set up Usages or use it day to day, so check its pages. Codex Forecast is a website with a public API [3], and it needs no account [3]. You can opt in to free emails sent when a reset happens [3]. The site and API share a snapshot cached for up to five minutes [3].

Things to check before you choose

Ask what you need to know. ccusage analyzes token usage and costs from local data [1], Usages monitors AI usage limits from an iPhone [2], and Codex Forecast estimates when Codex usage limits reset [3]. Ask whether a statistical estimate is enough for your planning, since that is what Codex Forecast gives [3]. Does each tool's own page say where your data is kept? ccusage works from local data [1]. Codex Forecast shares a snapshot cached for up to five minutes [3], and its public API needs no key [3]. Check which devices you use. Usages has an iPhone app [2] and a Mac version [2]. Check the cost of ccusage and Usages on their own pages, since the facts here give no price for either.

How to choose

If you want token and cost reports built from data on your own machine, ccusage is the tool whose sources describe that [1]. If you want to watch AI usage limits from an iPhone, Usages is the tool whose sources describe that [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]. If you need a public API that gives reset history without a key, Codex Forecast offers one [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]. Its free email alerts are sent when a reset actually happens, if you opt in [3]. The facts here give no other price for Codex Forecast, and none for ccusage or Usages, so check their own pages for any charge.

Does ccusage report costs?

Yes, its sources say it analyzes token usage and costs from local data [1]. Its cost columns and JSON cost fields can be removed with --no-cost, which hides cost figures from the output [1]. The facts here do not state a price for ccusage itself, so check its own page for any charge.

Is Usages available on Mac?

Yes, the facts here say Usages offers a Mac version [2]. Its main description is as an iPhone app for monitoring AI usage limits [2]. The facts here do not state a price for Usages. Check its own page for setup and cost details.

Can Codex Forecast tell when Codex usage limits reset?

Codex Forecast gives a statistical estimate of when OpenAI will next reset Codex usage limits [3]. 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 it uses is listed with a link to where it was announced [3].

What does the Codex Forecast API return?

Its public API needs no key and gives stats, paginated reset history, forecasts and operational health [3]. It has a published OpenAPI specification, which is a standard written description of how the API's requests and responses work [3]. The site and API share a snapshot cached for up to five minutes [3], so the figures you read can be up to five minutes old.

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

Try Codex Forecast

Sources

  1. ccusage, github.com/ryoppippi/ccusage, read 2026-11-07
  2. Usages, usages.app, read 2026-11-07
  3. Codex Forecast's own description of itself (the product of this site's publisher)

Related comparisons