codex startup_timeout_sec cannot be set manually (Codex)
Quick fix
Do not use CC Switch to manage Codex MCP instances that require a custom startup_timeout_sec for now.
Symptom
Section titled “Symptom”编辑中输入 startup_timeout_sec = 60 保存后不生效After entering startup_timeout_sec = 60 in the editor and saving, the setting does not take effect.
The maintainer confirmed that this is caused by the special format of the Codex configuration file; supporting custom fields like this would require substantial refactoring.
A user suggested appending TOML configuration in additional information or adding a field to the MCP JSON, but the original issue did not confirm that either approach was implemented or works. The issue was automatically closed due to inactivity and cannot be treated as fixed.
If you need to set a custom `startup_timeout_sec` for an MCP, do not use CC Switch to manage that MCP for now.
Follow the source issue; the original post does not provide a verifiable way to save this field in CC Switch.
Affected Versions
Section titled “Affected Versions”Source Issues
Section titled “Source Issues”This page is distilled from 1 real issues
- What if it also cannot be written through the general configuration?
- This is the same limitation. The maintainer said it is caused by the special format of the Codex configuration file, and the original post provides no verifiable solution within CC Switch.
- Can I add "startup_timeout_sec": 120 to the MCP JSON in the editor?
- This was a user suggestion. The original post did not confirm that it has been implemented or that the value is saved successfully.
Related problems
Section titled “Related problems”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.