Switch Codex accounts without logging out
The native Codex CLI is fine until you need more than one account. Then every account change turns into a relogin ritual. CodexUse fixes that by saving profiles locally so you can choose the active account first, keep projects separate, and stop burning time on the browser loop.
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.
- Once you juggle more than one account, re-authentication stops being a setup step and becomes workflow drag.
When multiple profiles 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, switching is a local profile choice, not a full relogin.
Desktop path
- Add each account once from the app.
- Pick the next profile from the tray, quick switcher, or main window.
- Start the next Codex session on that account.
What changes after the switch
- The next Codex session uses the newly active profile.
- Your saved profiles remain isolated locally, so you can move back and forth without deleting auth each time.
- If you also use Pro, rate-limit headroom and auto-roll layer on top of the same profile system.
Troubleshooting table
| Symptom | Likely cause | Action |
|---|---|---|
| Switch looks successful but the next run still behaves like the old account | The current shell or turn started before the switch | Open a fresh shell or start the next Codex session after switching |
| A profile says it needs login again | That saved auth expired or was revoked | Refresh the profile instead of deleting every account |
| Two profile names do not increase headroom | They point at the same OpenAI account | Merge or rename them so the profile list matches the real accounts |
Prevent it next time
- Name profiles by role, for example
personal,work, andclient-acme. - Switch before you start the next long task, not halfway through it.
- Keep one low-usage reserve profile ready if you regularly run into 429 windows.
Related
Can I switch Codex accounts without logging out?
Yes. CodexUse stores multiple profiles locally so you can switch the active account without repeating the browser login flow every time.
Why would I need more than one Codex profile?
Separate profiles help 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 profile apply to the current terminal instantly?
Usually it is safest to start the next Codex session or open a fresh shell after switching. Do not expect an already-running turn to change accounts mid-flight.