Codex OpenAI Official cannot participate in failover

Quick fix

Official providers are intentionally excluded from failover to avoid account-ban risks because a local proxy cannot fully simulate official requests.

Symptom

Error outputCopy

Codex OpenAI Official 无法参与故障转移，无法和第三方api丝滑切换

English translation

Codex OpenAI Official cannot participate in failover and cannot switch smoothly with third-party APIs.

Cause

This is feature-behavior feedback, not a confirmed bug fix. The report states that when switching from OpenAI Official to a third-party API, remaining `auth_mode` and `token` values in `auth.json` cause Codex to continue using official authentication. It suggests clearing or restoring these fields during switching.

The maintainer explicitly states that official providers do not participate in failover to avoid account-ban risks: a local proxy cannot guarantee full simulation of official requests. The original issue provides no verifiable solution and does not confirm implementation of the proposed authentication-field clearing and write-back logic.

Fix

1. 1

   The original issue does not yet provide a verifiable solution. Official providers currently do not participate in failover by design; follow the issue discussion for updates.

Affected Versions

ToolCodex

VersionUnknown

PlatformsUnknown

Source Issues

This page is distilled from 1 real issues

• #1248Codex OpenAI Official 无法参与故障转移，无法和第三方api丝滑切换

FAQ

(No FAQ yet)

Related problems

Auth conflictLog out of the official Claude login, clear conflicting ANTHROPIC_* variables, set hasCompletedOnboarding to true in ~/.claude.json, and restart the terminal.6 issues mergedClaude still asks to log in after configuration - Claude CodeAdd hasCompletedOnboarding: true to ~/.claude.json to skip the login prompt.4 issues mergedCannot configure additional upstream request headers in Claude DesktopThis is an unimplemented feature request; the original post provides no verified solution.1 issues merged