Connect Claude and Codex subscriptions
Connect your Claude and Codex subscriptions once, and every agent you launch on them starts signed in. Subscriptions & keys then shows every limit, how much of it is spent and when it comes back, so before bed you know which account has room for the night. API keys live on the same page: API keys covers them.

Connect a Codex subscription
Codex signs in with OpenAI's device code. Then every Codex you launch on your ChatGPT subscription starts signed in.
- In ChatGPT, open Settings → Security and switch on device code authorization for Codex. OpenAI refuses the code without it.
- In the dashboard, open Subscriptions & keys and pick Connect Codex.
- Pick Get code. The code expires 15 minutes after you get it.
- Pick Open OpenAI sign-in, paste the code on OpenAI's page and approve the sign-in.
- The dialog notices by itself and shows Codex connected.
If the code expires first, pick Get a new code and repeat steps 4 and 5.
Connect a Claude subscription
Connect it once, and every Claude Code you launch on it starts signed in.
- Open Subscriptions & keys and pick Connect Claude.
- Want Claude Code to work in the apps you connected on claude.ai, such as Gmail, Drive or Stripe? Tick Give Claude Code my claude.ai connectors. It starts unticked: agents act in those apps without asking.
- Pick Open Claude sign-in. Sign in with the account whose subscription the agents should use, and approve access.
- Claude's page shows a code. Copy it whole.
- Paste it into Paste the code from that page and pick Connect Claude.
A plug in the account's row means its connectors are on; the account's details show whether they are on or off. To turn them on or off, connect the subscription again with the tick set or cleared.
Connecting a different account than the one your browser uses? Pick Copy link and open the link in an incognito window or another browser.
Pick the subscription a launch runs on
The first account you connect of each provider becomes your Default. A launch runs on it unless you pick another:
- Open the project on Projects. Pick Edit on the default launch, or Edit in the ⋯ menu of a saved one.
- Under Runs on, pick Always my default or one account. The list groups accounts by provider and shows each one's plan, state or key balance.
- Pick Save. Terminals you open from now on start on it. Running terminals keep their account until you switch them from the terminal, as the next section shows.
Launches on Always my default follow it: open the row menu of another account on Subscriptions & keys, pick Make default, and they move with it. Several agents can share one account or run side by side on different accounts.
Your default accounts are also signed in in every home folder a terminal runs in, the shell's included, so claude and codex work in any terminal.
Switch a running agent to another account
The account a terminal runs on sits in the bar over it. Pick it to open This launch runs on:
- Every account the agent can use, with its live limits, such as
5h 40% · week 12%, or a key's balance. - An account it can't take right now is greyed out with the reason: signed out, a refused key, or a reserve held until a given time.
- Subscription rotation… (or Key rotation…) opens the rotation of this launch.
- Connect another in Subscriptions & keys takes you to the page to add one.
Pick an account, and Switch this launch to …? says what the agent does next:
| Agent | What happens |
|---|---|
| Claude Code moving between Claude subscriptions | It keeps working, and its next requests use the new account |
| Codex | It restarts on the same conversation now, or after the task it is on if it is busy |
| Anything else | After the switch the dialog offers Restart on this conversation; pick Later to keep the old access until the agent starts again |
The switch belongs to the launch, so its other running terminals take the new account too. Activity records each move.
Read your limits
Each account is one row: its main limit windows, the share already spent and the time left to each reset.
- Codex shows its 5-hour and weekly limits, plus limits per model.
- Claude shows its 5-hour and weekly limits, the weekly Opus and Sonnet limits, plus limits per model.
- The terminal count on a row lists the terminals working on that account now. Hover or tap it, and pick one to open it.
- Click a row to open its details: every window with its exact reset time, Codex resets, the reserve, the last problem reading the limits and when they were read.
Each provider's heading sums up its accounts, for example 2 of 4 used up. It turns red only when every account of the provider is out, or a login needs a fix.
Three numbers sit above the list:
| Figure | What it tells you |
|---|---|
| Ready for a long run | Accounts with every limit under 90 % and every key balance above its low mark |
| Next reset | The soonest reset across all accounts, with the account and the window |
| Need a fix | Logins or keys that stopped working |
Watch your limits from any page
The header of every dashboard page carries one chip per provider with the average load of its accounts. Hover it, or tap it on a phone, for every account's windows, resets and balances and the terminals Working on it now:. A red corner on a chip means a login or key stopped working. Open accounts goes to Subscriptions & keys.
Refresh the limits
The page reads limits live whenever the last reading is older than 5 minutes, and updates every minute while open. To ask again, pick Refresh limits on the row. Within 5 minutes of the last check you get that reading back instead of a new one. When a provider asks to slow down, the row keeps its last reading and names the time of the next check.
Spend a Codex limit reset
A Codex account that holds limit resets shows Resets available: with the count.
- Open the account row and pick Use a reset.
- Confirm. The spent Codex limit of that account resets right away.
A reset can't be undone. Nothing in detachbox spends one on its own, and a reset asked for while no limit is spent is kept for later.
Keep part of a subscription for yourself
To share a subscription with your agents while you use it elsewhere, set a reserve: pick Keep a reserve in the row's menu and enter the share of the 5-hour and weekly limits to keep. Keep a reserve covers what agents do at the line, and how to lift the reserve until the week resets.
Share a subscription with a teammate
A teammate with a detachbox account of their own can connect the same subscription or API key. Both accounts then share one reading of its limits, and a key the provider refuses stops working for both.
When an account signs out
A subscription can lose its login. Its row then reads Signed out, and the agents on it stop until you reconnect. You get an email with a link back to the connect step.
- Pick Reconnect on the row.
- Sign in to the same account again.
The account keeps its place in every launch and stays your default if it was one. A separate email tells you when a nearly spent limit resets, at most once a day per account.
Disconnect an account
- Open the row's menu and pick Disconnect.
- Confirm.
We remove the login from our server at once and from your terminals: running ones right away, the others when they next start. Launches that ran on it move to your default subscription. With no default left, their agents sign in inside the terminal, and that login stays in the project's own home folder. Disconnect your default and the oldest account left of that provider takes its place.
Where your tokens live
- The refresh token stays on our server, encrypted with AES-256-GCM. It never reaches your Compute.
- Your Compute gets a file with an access token only: in the launch's folder inside the project for its terminals, and in
~/.codex/auth.jsonand~/.claude/.credentials.jsonof each home folder for your default accounts. Our server renews it before it expires. - Disconnecting an account deletes its tokens from our server and from your terminals. It does not sign you out at OpenAI or Anthropic; do that there to end the provider's session too.
On your laptop, sign in to Codex and Claude separately. Never copy auth.json off your Compute: it holds an access token that our server renews for detachbox only. Read more on /security.
detachbox is an independent service. Claude Code and Codex come preinstalled as their makers ship them, under their own terms.