Official Codex app orchestrator for multiple accounts
The official Codex app is now a first-class part of the CodexUse workflow. CodexUse can detect profile-matched Codex app windows, show which account is running, and orchestrate the window from the same place you manage Codex CLI profiles.
Why this matters
Most Codex multi-account workflows start with the CLI because CODEX_HOME gives each profile its own auth and config. The official Codex app adds another surface: visual sessions, app-server state, and windows users expect to focus or restart like normal macOS processes.
If you use personal, work, and client accounts, the hard part is not only saving auth. It is knowing which Codex surface is attached to which account, stopping the right window, and relaunching with the correct profile before a long task.
Why orchestrator, not just switcher
A switcher changes the active account. An orchestrator tracks the running surfaces attached to those accounts. Codex Apps starts there: profile-backed windows, live process state, and direct controls for the official Codex app. That gives CodexUse the base layer for later handoff and shared-session ideas without pretending those behaviors ship today.
What Codex Apps orchestrates
- Launch: open the official Codex app with a selected CodexUse profile.
- Detect: map already-open official Codex app windows back to saved profiles when their account matches.
- Focus: bring the matched Codex app window forward.
- Stop: stop the matched macOS process tree.
- Restart: stop the matched window, then launch a fresh one with that profile.
- Live state: show running state, PID, app-server PID, and uptime.
How this fits with CLI profiles
CodexUse still keeps profiles local. You save each account once, switch from the tray, desktop app, or CLI, and keep project work separated from quick Chat/Agent sessions. Codex Apps extends that same profile layer to official Codex app windows.
codexuse profile list
codexuse profile switch work
codexuse account-pool statusWhen to use Codex Apps vs Accounts Pool
| Need | Use |
|---|---|
| Open, monitor, or restart the official Codex app under a specific account | Codex Apps |
| Switch the active Codex CLI profile before a terminal run | Profiles or CLI |
| Let another OpenAI-compatible tool share saved account quota | Accounts Pool |
| Move before an account runs out of usage | Rate-limit headroom and auto-roll |
Guardrails
- CodexUse does not claim extra quota. It makes account state, switching, and routing explicit.
- Stopping or restarting a window affects the matched official Codex app process.
- If a long-running turn is active, finish or save the work before restarting the window.
- Codex Apps does not hand off an active official Codex task between accounts yet.
- Accounts Pool is local. It is not a hosted cloud API.
FAQ
Can the official Codex app run with multiple accounts?
CodexUse can launch official Codex app windows with profile-specific Codex homes, detect already-open profile-matched windows, and orchestrate focus, stop, restart, launch, and live process state from one local settings pane.
Does CodexUse require OpenAI API keys for Codex Apps?
No. CodexUse uses the same OAuth login model as Codex CLI. Accounts Pool can create a separate local key only when another OpenAI-compatible client talks to CodexUse's local API.
Does Codex Apps hand off active tasks between accounts?
Not yet. Current Codex Apps scope is profile-aware official Codex window and process orchestration. Auto-handoff and shared session context are future product directions.