Skip to content
CC Switch WikiUnofficial Community Wiki

Codex configuration still includes `disable_response_storage = true`

Quick fix

No verified fix is available. A PR proposes removing disable_response_storage from generation paths, but its merge or release is unconfirmed.

Symptom

Section titled “Symptom”
Error output
最新稳定版 v3.20.3 及当前 main 的多个实际生成路径仍包含 `disable_response_storage = true`，容易让用户误以为它仍是可控制服务端回复存储的有效开关，也给配置排查和清理增加歧义。
English translation

Multiple actual generation paths in the latest stable version v3.20.3 and current main still include `disable_response_storage = true`. This can mislead users into thinking it remains a valid switch for controlling server-side response storage and adds ambiguity to configuration troubleshooting and cleanup.

Cause

Section titled “Cause”

According to the report, upstream Codex removed the disable_response_storage setting and sets store directly to false in Responses requests. CC Switch 3.20.3 and the main commit reviewed in the report still generate the obsolete field through custom provider templates, third-party presets, unified providers, and deeplink imports. The field therefore cannot provide the corresponding storage control in current Codex. The report is based on source inspection, without GUI regression testing or observed startup or request failures caused by this field. A later comment reports an ignored-setting warning.

A commenter said they submitted PR #7556 to clean up generation paths and related previews, examples, and documentation while preserving compatibility with reading the old key in existing configurations. This is a submitted fix proposal; the supplied discussion does not confirm a merge, release, or successful user verification. The issue remains open.

Fix

Section titled “Fix”

  1. Identify this as an obsolete configuration generation issue. The thread does not establish that it causes startup or request failures, and the field cannot be treated as a valid storage control switch in current Codex.

  2. The thread provides no verified fix. Follow PR #7556 mentioned in issue #7524 to confirm whether the generation cleanup has been merged and released. The current discussion provides no fix version to recommend.

  3. Distinguish new configuration generation from migration of existing configurations. The proposal submitted in the comments preserves existing configurations and compatibility with reading the old key. It does not claim to automatically remove the field from existing configurations.

Affected Versions

Section titled “Affected Versions”
ToolCodex
Versioncc-switch 3.20.3（受影响版本）；Codex CLI 0.155.1（报告环境）
PlatformsLinux

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”
Request exceeds the context windowNo verified solution was provided in the original post; this issue was closed as a duplicate related to catalog configuration and automatic compression.1 issues mergedCrash on Launch: CC Switch Windows Startup CrashReproduce on the latest version and provide the CC Switch, Windows, and WebView2 versions, along with the latest logs and Event Viewer error details.1 issues mergedCodex provider writeback resets live UI settings from configUpgrade to cc-switch v4.0 or later. Provider switching updates only key fields and preserves the rest of ~/.codex/config.toml.7 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.