Skip to content
CC Switch WikiUnofficial Community Wiki

Codex custom endpoint silently redirected to chatgpt.com (withdrawn)

Quick fix

Report withdrawn: the redirect affected only an unmerged commit. Routing works in existing versions; no configuration changes are needed based on this report.

Symptom

Section titled “Symptom”
Error output
用户配置的自订端点被静默绕过，且没有任何错误提示。
English translation

The user's configured custom endpoint was silently bypassed without any error message.

Cause

Section titled “Cause”

The original report stated that a Codex provider linked to a managed OAuth account and configured with a custom endpoint was routed to chatgpt.com/backend-api/codex after local routing takeover was enabled. The author initially suspected that is_codex_official_provider determined both the credential source and the upstream destination, causing extract_base_url to ignore the custom upstream. The report also described inconsistent frontend check ordering that blocked switching during takeover and displayed an incorrect badge.

The author later withdrew the report, clarifying that the redirect came from a commit in an unmerged PR. The issue does not currently exist upstream, and routing for these cards works in existing versions. Existing versions have a separate issue where auth.json is not written; this must not be conflated with the redirect report. The backend upstream resolution and frontend check ordering changes described in the post were proposed branch fixes. The author said they would include them in the relevant PR, but the thread provides no verification of a merge or release. Closure indicates withdrawal, not a released fix.

Fix

Section titled “Fix”

  1. Confirm the report's scope first: the author withdrew it and confirmed that custom endpoint routing works in existing versions. Do not change configuration solely based on this thread.

  2. If you are testing the relevant unmerged commit, follow the PR referenced in the source thread. The original post provides no verifiable solution. Although it states that the branch fix was completed, it provides no record of a merge, release, or successful verification.

  3. If the actual symptom is that auth.json is not written, investigate it separately as a credential synchronization issue. The withdrawal explicitly distinguishes it from the takeover redirect issue on this page.

Affected Versions

Section titled “Affected Versions”
ToolCodex
VersionUnknown
PlatformsUnknown

Source Issues

Section titled “Source Issues”

This page is distilled from 1 real issues

FAQ

Section titled “FAQ”

(No FAQ yet)

Section titled “Related problems”
Gtk-CRITICAL: gtk_widget_get_scale_factor failedOn a GTK assertion failure running cc-switch under Linux or WSL2, edit settings.json to turn silent startup off, or clean the leftovers and reinstall.3 issues mergedProvider API Key Overwritten: After Codex Restart or SwitchUpgrade to cc-switch v4.0.0 or later to prevent provider keys from overwriting each other and restore the official login state.6 issues mergedSwitching Codex providers overwrites config.tomlUpgrade cc-switch to v3.17.0+ and sync the MCP and other settings you want to keep into “General Configuration”; if an old snapshot still writes them back…21 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.