Account free limit resets

Accounts shows free and earned reset offers for the selected Claude or Codex account. These are separate from purchased credits and the scheduled five-hour or weekly quota reset clocks. Only a fresh official observation establishes a remaining count. Missing metadata, failed reads, unsupported authentication, reported zero, stale observations and partial details remain distinct.

Shift+L (configurable as accounts.limit-reset) opens the selected account's verified Codex reset confirmation when its native capability is available. The confirmation names the account, shows the banked count, and says that Codex will choose the next available earned credit. Press Y or click Use one reset to confirm; Esc cancels. Opening the dialog does not consume a reset.

Missing native capability, unsupported authentication or an unverified CLI version produces account-specific instructions instead. Claude keeps its provider-specific guide: in the official web or Desktop app, first verify the signed-in identity matches the selected account, then review Usage and confirm any offer there. devctrl does not open a generic Usage URL, choose a browser profile, log out or switch identities, or send commands to active sessions.

Codex earned resets

The existing official CLI app-server probe reads account/rateLimits/read with the selected account's isolated CODEX_HOME, account UID and configured network route. It does not use the operator's global Codex or a browser login. Existing credential-store locks and account ownership checks remain in effect.

When the service reports rateLimitResetCredits.availableCount, Accounts shows that count, including an explicit zero. For example, a count of two displays two banked resets even if the response contains one detail row, no rows or null details. The count is authoritative; detail rows can be capped. Only sanitized status, reset type and grant/expiry times are retained. Opaque credit IDs, titles, descriptions and credentials are omitted.

Known expiry is shown as the next reported expiry, since other credits may lack details. An observation becomes stale when a known available credit expires; devctrl refreshes rather than subtracting a partial list or guessing a new count. The native confirmation determines eligible windows. The codexRateLimits type does not by itself describe a five-hour or weekly grant. Paid credit balances and resetsAt quota clocks never become earned resets.

The official app-server documentation defines the account-bound account/rateLimitResetCredit/consume RPC. A confirmed request uses the selected account's native identity, isolated file authorization, network generation and an immutable logical UUID. A completed reset is followed by an official usage read. An uncertain result retains the original UUID; only an explicit retry reuses that attempt. devctrl does not automatically retry with a new key or infer fresh quota from an offer. Refreshing Accounts and ordinary polling never consume resets. Protocol tests use synthetic CLI/RPC fixtures and never redeem real credits.

Claude offers

Claude's read-only collector keeps its existing cedar_ember=1&skip_spend=1 usage mode from official Claude Code 2.1.292, with ordinary usage fallback. Eligibility, bounded grant counts, covered limits, pause, start and expiry come from provider fields. juniper_tide eligibility is retained without inventing a remaining-reset count. The legacy claudeLimitReset observation remains readable alongside the reusable accountLimitReset model during upgrades.

A surface refusal describes this connection, not a zero account allowance. Claude's official web or Desktop confirmation remains authoritative for eligibility and consequences; this feature does not invent a Claude CLI reset action. See What is a limit reset?. Account polling retains its existing five-minute schedule and never restores launch admission merely because a free-reset offer exists.