Usage
Plan limits
Watch your Claude, Codex and Cursor plans fill up, with projections and reset times, in the menu bar, a widget and the app.
Claude, Codex and Cursor subscriptions come with limits: rolling windows that fill as you work and reset later, or an allowance for the billing cycle. Codz shows how full each one is, where a Claude window is heading at the pace you’re going, and when a Codex window resets, so a limit doesn’t catch you halfway through a task.
Plan limits are part of the free app and need no Codz account.
What Codz reads
Claude
Claude’s 5-hour and 7-day windows, and its extra usage when that is in use. The readings come from the Claude desktop app, which records them on this Mac while it is running, so they describe the account the Claude app is signed in to.
Codz measures the pace of the recent readings and projects each window forward:
- “~59% by reset”: where the window lands if the pace holds. Bars draw this as a lighter extension of the fill.
- “runs out in 1h 40m”: the window fills before it resets, and the meter turns orange.
- “idle” and “spent”, with the time to the reset where Codz can work it out.
- “paused · 50m old”: the newest reading is too old to describe the window you’re in, usually because the Claude app hasn’t been running. Codz stops projecting until a fresh reading arrives.
Claude doesn’t state when a window resets. A window opens with the first message after the last one ended, and Codz dates it from the readings, so a Claude reset time is an estimate.
Codex
Codex reports each window itself, commonly a 5-hour and a 7-day one, with the exact time it resets. Codz asks each Codex login for them every couple of minutes and shows a countdown, such as “resets in 4h 12m”, without projecting. When a window resets, it drops off until Codex reports the new one after your next request.
If you use more than one ChatGPT login with Codex, each login’s windows are read separately and named by login. A model with a limit of its own is listed under the model’s name. See Providers & logins.
Cursor
Cursor’s included usage for the current billing cycle, as a percentage, with “$12.40 remaining” or “No included usage left” when your account reports a balance. It comes from your Cursor account, so it appears while the Cursor app is signed in on this Mac. Cursor reports no history or cycle end, so there is no projection.
Other providers
OpenRouter shows the spend limit set on your key, such as “$3.40 of $10.00”, or No spend limit set. OpenCode says Plan limit not reported, and DeepSeek Usage not collected.
Where you see them
| Where | What it shows |
|---|---|
| Menu bar | Plan limits: every window, with its projection or countdown |
| Plan Limits widget | The window most at risk (small), or up to three (medium) |
| Overview | One plan meter: Cursor’s cycle, else Claude’s 5-hour window, else Codex’s fullest window |
| Account menu | Plan limits under your name: the fullest provider, then one row per provider |
| Composer | A Plan section in the context meter’s popover, for the chat’s provider |
| Usage ▸ Capacity | Every window with its projection (Pro) |
codz status | Each provider’s windows, Claude’s forecasts and Cursor’s cycle |
In the account menu, a provider with several windows opens a submenu with each one and, for Codex, when it resets. Providers with nothing to report are folded into one row, such as “2 others with no reading”, whose submenu says why for each. Clicking a row opens Usage.
The model picker shows the reading beside a provider’s logins, and each Codex login has its own. codz status asks Codex for its windows as it runs, and codz status --json puts every reading under plans. See Commands.
Colours
In the menu bar, a bar is drawn in its provider’s colour while there’s room. It turns orange from 75%, or sooner when a Claude window is on pace to run out before it resets, and red from 90%. The Plan Limits widget keeps the provider’s colour and turns the percentage amber when a window is on pace to run out.
When a plan runs out
When a provider refuses a turn because its limit is spent, the chat says so above the composer, for example “You’re out of Claude usage”, with what the provider suggests and when it resets.
With Continue on another provider turned on in Settings ▸ Agent & composer, Codz keeps the task going on the next ready model in your loadout instead of stopping. It is on by default. See Models & loadout.
Questions
There’s no Claude meter. Claude’s readings come from the Claude desktop app. Install it, sign in to the account you use with Claude Code, and keep it running. Until it has recorded a reading, the Plan Limits widget says “No plan meters yet. Claude reports them while Claude Desktop runs; Codex on its next request.”
A Claude meter says “paused”. The newest reading is old. Open the Claude app and the meter picks up again with its next reading.
Codex says “Plan limit unavailable”. Codz couldn’t ask Codex, or every window it reported has since reset. Check that the Codex CLI is installed and signed in (codex login); after a reset, the next request reports the new windows.
Cursor’s cycle is missing. Sign in to the Cursor app on this Mac. Codz shows Cursor’s account usage only when that service answers.