Skip to content

Disable response strange: Codex configuration failure

Quick fix

Check ~/.codex/config.toml for deprecated disable_response_storage, then share the configuration and startup error with maintainers.

Error output
本地 Proxy 首次初始化,与本地路由处理冲突,产生异常 key `Disable response strange`,致使配置整体失效,URL 被重定向至官方链接
English translation

During initial local Proxy setup, it conflicts with local route handling and produces the unexpected key `Disable response strange`, causing the entire configuration to fail and the URL to be redirected to the official link.

A maintainer stated that `Disable response strange` could not be generated directly by CC Switch; it may be a paraphrase of the UI text “Disable response storage.” The maintainer inferred that CC Switch might still write the deprecated `disable_response_storage` to `~/.codex/config.toml` during initial local proxy setup.

  1. Check the full contents of `~/.codex/config.toml` (redact the API Key). Confirm whether `disable_response_storage` exists and whether it is at the top level or in a `[model_providers.*]` table.

  2. Record the exact Codex CLI/Desktop version and startup error text. In particular, check whether it contains `unknown configuration field`, then submit it to maintainers so they can evaluate how to migrate existing configuration.

ToolCodex
VersionUnknown
PlatformsWindows

(No FAQ yet)

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.