Codex on Linux with multiple profiles
Linux is a strong Codex environment until one account is not enough. If you move between work, client, and personal sessions from the same terminal-heavy machine, CodexUse gives you named profiles, fast switching, and a cleaner way to keep reserve headroom for the next 429 window.
Why this happens
- The native Codex CLI keeps one active login at a time.
- Linux workflows often mix local terminals, SSH sessions, and multiple client contexts in the same day.
- When rate limits land, you need a clean way to move to another account without repeating the whole login loop.
Fast fix
CLI-only steps
- Add each account once with a clear name.
- Use device auth when you are on SSH or a headless Linux box.
- Switch before the next long Codex turn, then start a fresh shell or session.
CodexUse path
- Use the Linux app to keep profiles visible from one local control point.
- Use the CLI when you want the same workflow in tmux, SSH, or a remote box.
- If your main machine already has the right setup, pull it onto Linux with cloud sync.
codexuse profile add Work --login=device
codexuse profile add Personal --login=device
codexuse profile list --compact
codexuse profile switch Work
codexuse profile autoroll --dry-runUse --login=browser on a normal desktop Linux session if you prefer the browser flow.
Cross-device handoff is where Linux gets better
If your main setup lives on a MacBook or another Linux box, push from there and pull onto the Linux machine that is about to do the work.
Prevent it next time
- Name profiles by role, for example
work,client-acme, orpersonal. - Keep one lower-usage reserve profile ready for when the primary account is close to a 429.
- Use
profile autorollor a manual preflight before big jobs instead of waiting for interruption.
Troubleshooting table
| Symptom | Likely cause | Action |
|---|---|---|
| Switched profiles but the next command still feels tied to the old account | The shell or Codex turn started before the switch | Open a fresh shell or start the next session after switching |
| You get a duplicate-account warning | Two profile names point at the same OpenAI account | Merge or rename them so the local profile list matches reality |
| You are on SSH with no browser access | The auth flow is mismatched to the environment | Use device auth and stay in the CLI path |
What to avoid
- Using the same OpenAI account under multiple profile names just to fake more capacity.
- Starting a long run before you confirm which profile is active.
- Assuming an already-running session will inherit a new profile switch mid-turn.
Related
Can I run CodexUse on Linux?
Yes. CodexUse ships Linux installer archives for ARM64 and x64, and the CLI works well for terminal-heavy or SSH-heavy workflows.
Why would I need multiple profiles on Linux?
Linux workflows often mix client, work, and personal terminals. Multiple profiles keep those accounts separate and make it easier to switch before a long run or a 429.
Does profile switching apply to the current session 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 inherit the new active profile.