Claude Code and Codex accounts, quota, and auto-continue
Add Claude Code or Codex accounts, inspect usage, switch a chat's account, and choose whether to wait or switch when a limit is reached.
atrium can register several Claude Code or Codex accounts, show their quota, and continue a chat on another account when needed. Account selection is available in the launcher and agent chat; terminal account switching is not enabled.
Other adapters can report session usage according to their capabilities. Custom API providers are configured separately from subscription accounts.
The account chip
A user-icon account chip appears in the launcher before a session exists. In chat, account controls live in the combined usage/context ring's popover.
Its ring shows the account's reported quota windows. Open the popover for the current identity, other accounts, usage and reset times, and Auto-continue settings. Context usage remains a separate session measurement.
Usage readings carry their age. An unavailable or stale reading does not mean that an account has no limit; refresh a row to ask for a current reading.
Adding an account
Choose Add in the account popover and finish the sign-in in your system browser:
- Claude Code: signs in to an isolated account store, which can refresh its credentials and usage. The separate Token action is a fallback that authorizes twice and creates a long-lived setup token; that token can run Claude but cannot refresh quota.
- Codex: signs in to an account-specific Codex home. If device authorization is needed, the popover shows the code to enter in your browser. The account appears once its identity is confirmed.
An account marked Needs re-auth cannot be selected for failover until its sign-in is repaired. Use Sign in again where offered. A Claude apiKeyHelper can override account credentials; the popover reports when one is configured.
Switching
Select another account in a chat's popover. atrium switches the engine credentials and resumes the conversation under that account. Other running panes keep their bindings; the selection also seeds the default for future launches.
Manually switching during work can interrupt the current turn. atrium records the interruption and reopens the session with the selected account.
Auto-switch
The Auto-continue settings decide what happens after a usage limit. You can set a default and override it for one conversation:
- Wait here — wait for the current account's reset, then continue.
- Switch accounts — switch to another usable account when one is free; otherwise wait.
| Strategy | Behavior |
| Least used | Fail over to the account with the most headroom. Spreads load evenly. |
| Most used | Use the fullest available account first. |
| Soonest reset | Prefer the account whose constraining window resets soonest. |
| Latest reset | Prefer the account whose constraining window resets latest. |
While waiting, the account control shows when the conversation is expected to continue. Switching accounts does not change the underlying provider or tool. Task cards have a separate launch fallback list that can choose another adapter before a run begins.
Accounts are location-scoped. A server does not automatically receive credentials stored on this computer; review its Credentials in Settings → Locations. Forwarding or creating credentials on a server requires consent. For a paired desktop computer, the account display identifies the account signed in there; manage that computer's accounts on the computer itself.
Watching usage
The composer's usage ring reports context consumption for the current session, with a breakdown popover and a Compact action. For Claude Code panes, the same popover leads with your account's 5-hour and weekly limit windows, so context pressure and quota pressure are readable in one place. Codex panes show their plan-quota windows the same way. Every adapter with a known provider dashboard also offers a View usage limits link that opens that page in your system browser.