Skip to content
CC Switch WikiUnofficial Community Wiki

Unknown parameter: 'input[115].namespace' - Codex

Quick fix

Turn the cc-switch unified session history switch off and move sessions tagged custom back to openai, fixing the namespace parameter error.

Symptom

Section titled “Symptom”
Error output
[ObjectParam] [input[115].namespace] [unknown_parameter] Unknown parameter: 'input[115].namespace'.

Cause

Section titled “Cause”

Using the Codex enhancement features in cc-switch changes the underlying config in ways that conflict across versions. Enabling 统一会话历史 (unified session history) injects a custom tag into official subscription sessions, so requests carry an unknown namespace parameter and error (some users see input[7].namespace).

The cluster also holds related config conflicts from before v3.17.0: enabling 切换第三方时保留官方登录 (keep the official login when switching to a third party) forcibly overwrites the third-party auth.json, so the API key cannot be saved or you cannot switch straight back to an official account.

Fix

Section titled “Fix”

  1. To resolve the Unknown parameter error: turn 统一会话历史 (unified session history) off in cc-switch, and move history sessions from the custom bucket back to openai by hand, keeping multi-model sessions separate.

  2. To resolve the API key not switching or auth.json being overwritten: upgrade cc-switch to v3.17.0 or newer and turn 切换第三方时保留官方登录 (keep the official login when switching to a third party) on by hand under 设置 -> 通用 -> Codex 应用增强 (Settings > General > Codex app enhancements).

Affected Versions

Section titled “Affected Versions”
ToolCodex
Version3.16.1 - 3.18.0
PlatformsWindowsmacOS

Source Issues

Section titled “Source Issues”

This page is distilled from 4 real issues

FAQ

Section titled “FAQ”
Does fixing the Unknown parameter error affect my session history?
Yes, it does. After turning the unified session switch off, move the sessions in the custom bucket into openai, or use another agent to help repair config.toml.
I still cannot switch API key after upgrading to v3.17.0. What now?
Report back with the relevant redacted fields from auth.json or config.toml, the full switching sequence, and logs.
Section titled “Related problems”
auth.json refilled with an existing account's auth.json - CodexUpgrade to v3.17.0+ and turn off 非接管切换时保留官方登录 (keep official login on non-takeover switch). Back up auth.json before upgrading.22 issues mergedbuilt-in provider IDs: openai - CodexUpgrade CC Switch to v3.16.4+, delete the old config and save again. Enable unified Codex session history and use openai_base_url.3 issues mergedcodex session expired - CodexBack up the config, then sync the auth.json token into the cc-switch database with a script, or turn usage refresh off so old data cannot overwrite it.5 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.