Open another Codex account without logging out
The Codex CLI is fine with one account. Add a second and every change of account becomes a relogin ritual. CodexUse saves each account locally and gives each one its own Codex window, so you Open the account you want, keep client and personal contexts separate, and never touch the browser login loop again.
Why the native flow gets painful
- The CLI effectively works with one active login at a time.
- Client, team, and personal work often need different accounts for billing, audit, or quota reasons.
- Past one account, re-authentication stops being a setup step and becomes daily workflow drag.
When multiple accounts actually matter
- Client separation: keep each customer on the right account from the start.
- Personal vs work: avoid mixing sessions, limits, and history into one local state.
- Reserve headroom: move to another account when the current one is getting hot.
Fastest path
codexuse profile list --compact
codexuse profile add Client-A --login=device
codexuse profile switch Personal
codexuse profile currentAdd each account once. After that, choosing the account the Codex CLI uses next is a local choice, not a full relogin.
Desktop path
- Add each account once from the Accounts tab.
- Select the account and click Open. If its Codex window is already running, the button reads Show and brings that window forward. Press ⌘K to jump to an account by name.
- Start the next Codex task in that window. Every other account keeps its own window running and signed in.
What changes after you Open another account
- On the desktop, nothing moves. The account you opened has its own Codex window, and the other windows stay where they were.
- In the terminal, the next Codex CLI session uses the account you selected.
- Your saved accounts remain isolated locally, so you can move back and forth without deleting auth each time.
- Rate-limit headroom and Auto-roll layer on top of the same account list.
Troubleshooting table
| Symptom | Likely cause | Action |
|---|---|---|
| The CLI shows the new account but the next run still behaves like the old one | The current shell or turn started before you changed the account | Open a fresh shell or start the next Codex session after changing the account |
| An account shows Needs sign-in | That saved auth expired or was revoked | Refresh that one account instead of deleting every account |
| Two account names do not increase headroom | They point at the same OpenAI account | Remove or rename them so the account list matches the real accounts |
Prevent it next time
- Name accounts by role, for example
personal,work, andclient-acme. - Open the account you want before you start the next long task, not halfway through it.
- Keep one low-usage reserve account ready if you regularly run into 429 windows.
Related
Can I change Codex accounts without logging out?
Yes. CodexUse stores multiple accounts locally. On the Mac, each account has its own Codex window that you Open or Show. In the terminal, you pick which saved account the Codex CLI uses next. Neither repeats the browser login flow.
Why would I need more than one Codex account?
Separate accounts keep work, client, and personal usage isolated. They also make it easier to move to another account when one is near a rate limit.
Does the new account apply to the current terminal instantly?
Usually it is safest to start the next Codex session or open a fresh shell after changing the account. Do not expect an already-running turn to change accounts mid-flight.