Codex quota and reset credits on Mac

At a glance

What you see

Every window the service returns, labelled by its own duration — weekly for a seven-day window, otherwise by hours or minutes. Alongside them, the number of resets the service says are still available.

How the account is named

The email from the engine together with the account id. Members of one workspace share an account id, so the email is what separates their quota; an engine that cannot report the email shows the workspace alone.

Running turns and completions

Both running turns and completions are detected. Sub-agent and guardian sessions are excluded, and one session counts once even after it is archived.

What Agent HUD reads

The rollout logs and the session index, decoding only the lines that describe a session, its context and its events. It uses the engine's own sign-in and never reads the stored credentials file.

Common questions

Do Codex Desktop and the Codex CLI have separate quotas?

No. On one Codex home they share one set of windows, and usage from one is never copied into the other. Separate homes are kept separate.

What is the reset credit count?

The number of resets the service reports as available. Agent HUD shows that number as given; the per-credit expiry list beside it is supplementary and is never used to work the count out.