Skip to content
CC Switch WikiUnofficial Community Wiki

Unified Codex Session History Not Working: Sessions Do Not Merge

Quick fix

Upgrade to cc-switch v4.0.0 or later and enable “Unified Codex Session History” so official and third-party routes share a history group.

Symptom

Section titled “Symptom”
Error output
选择了 统一Codex会员历史 ，但是切换服务商的时候，官方的和第三方的历史会话还是不会合并，官方的只能看到官方的历史会话，第三方的还是只能看到第三方的历史会话。
English translation

After selecting Unified Codex Session History, switching providers still does not merge official and third-party sessions. The official route shows only official sessions, and the third-party route shows only third-party sessions.

Cause

Section titled “Cause”

When the official OAuth route is enabled, it uses a separate model_provider (cc-switch-official), so official, third-party, and official OAuth routes may form different history groups. After switching providers, sessions from other groups may not be visible. Earlier reports also noted that OpenAI Official uses access_token and refresh_token, while regular custom providers use api_key; the different authentication methods can isolate session groups.

Fix

Section titled “Fix”

  1. Upgrade to cc-switch v4.0.0 or later; the maintainer said that from v4.0.0 onward, the official route uses the same identifier as the direct route.

  2. Enable “Unified Codex Session History,” then switch routes and check the sessions. If you still need to view, manage, or restore history that remains separated into groups, use the session management entry point.

Affected Versions

Section titled “Affected Versions”
ToolCodex
Version3.17.0（问题版本）；v4.0.0 起修复
PlatformsWindows

Source Issues

Section titled “Source Issues”

This page is distilled from 2 real issues

FAQ

Section titled “FAQ”
After switching to OpenAI Official, why can’t I see sessions from my previous custom provider?
In the early implementation, OpenAI Official used access_token and refresh_token, while regular custom providers used api_key. As a result, history was grouped by authentication method. The maintainer said that from v4.0.0 onward, the official route uses the direct-route identifier; on earlier versions, use session management to view, manage, and restore the relevant sessions.
How can I keep sessions visible when switching between multiple regular custom providers?
An issue comment suggested using a local route, assigning the same group name and name to multiple providers, then switching by controlling whether each provider is included in the route.
Section titled “Related problems”
Shared MCP not working? CodexUpdate to the latest CC Switch and share Claude MCP again. If Codex still cannot see it, provide the version number and the mcp_servers section from…1 issues mergedCloud Sync Runs Automatically the First Time the App Opens Each DayUpgrade to 4.0 or the latest version and retest. If it persists, reopen the issue with complete steps, logs, or screenshots.1 issues mergedKeep official login has no effect; Codex shows API loginUpgrade to cc-switch v4.0.0 or later; this version changes how Codex configuration is written to prevent third-party provider keys from replacing official…1 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.