v2.4.0
August 13, 2026 · View on GitHub
Adds --account to the wrapper, so you can force a single run onto one account.
npm i -g codex-multi-auth
Additive. If you don't use the flag, nothing changes.
Forcing an account
codex-multi-auth-codex --account 2 "your prompt"
codex-multi-auth-codex --account you@example.com "your prompt"
The selector takes a 1-based index (matching codex-multi-auth list), an email, or an account id. All-digit selectors are always read as an index. CODEX_MULTI_AUTH_FORCE_ACCOUNT=<selector> does the same for tools that find env vars easier than flags; the flag wins if you set both.
Two properties worth knowing:
It's ephemeral. The pin applies only to that one invocation and never touches your persisted switch pin. Run three commands with three different --account values at once and they won't interfere.
It fails hard. The session never rotates. If the account you picked is rate-limited or unavailable, the request fails rather than quietly using a different one. Same if the selector doesn't resolve, or if rotation is disabled — the wrapper exits non-zero without launching Codex.
That's deliberate: if you asked for a specific account, silently billing a different one is worse than an error.