Short answers for developers evaluating codex-multi-auth.
No. codex-multi-auth wraps the official @openai/codex CLI. It handles codex auth ... locally and forwards the rest of the codex workflow to the official CLI.
It makes multi-account OAuth state visible and operable. Instead of relying on one hidden local auth state, you can sign into multiple accounts, switch explicitly, run health checks, and repair local storage issues.
Not for the ChatGPT-authenticated multi-account workflow in this repository. If you are building production applications or API integrations, use the OpenAI Platform API instead.
No. Many users only need the wrapper and codex auth ... commands. The plugin-host runtime is optional and uses the same account pool for advanced host request handling.
Runtime rotation is enabled by default for request-bearing forwarded Codex CLI/app sessions. Disable it with codex auth rotation disable, codexRuntimeRotationProxy=false, or CODEX_MULTI_AUTH_RUNTIME_ROTATION_PROXY=0 when you need plain official Codex forwarding.
No. The packaged app bind updates user-level Codex config and startup/router metadata and keeps a backup for restore. Official app binaries are not patched.
This project is aimed at individual developers using the official Codex CLI who want more control over local account state, switching, diagnostics, and recovery.
No. The repository is positioned for personal development workflows with your own accounts.
By default, under ~/.codex/multi-auth. Project-scoped account pools can also live under ~/.codex/multi-auth/projects/<project-key>/....
Run:
codex auth doctor --fix
codex auth check
codex auth forecast --liveThen rerun codex auth login if the affected account still looks stale.