#MCP settings save fails after editing startup_timeout_ms / stale MCP config snapshot

1 messages · Page 1 of 1 (latest)

tall shoalBOT
#

Reported by @onyx shoal

Bug Report: MCP settings save fails after editing startup_timeout_ms / stale MCP config snapshot
`Steps to Reproduce`
  • Open Codex in VS Code.
  • Open MCP server settings for an MCP server.
  • Change a setting and press save.
  • Ensure ~/.codex/config.toml contains startup_timeout_ms for the server, e.g. 10002.
  • Open MCP server settings for the MCP server.
  • Edit any visible MCP field, then click Save.
  • Reopen the MCP settings. At this point the setting save works.
  • Make another change, and press save.
  • Reopen the MCP settings. At this point the setting save does NOT work.
`Expected Result`

Saving settings always works.

`Actual Result`

Saving settings does not work, unless manually editing the config.toml to include the field 'startup_timeout_ms' instead of 'startup_timeout_sec'.

`Environment`

VS Code Codex plugin (26,519,32039) - Fedora KDE

#
Additional Information

Please provide relevant details to help resolve the issue, such as:

  • ChatGPT Shared Link (if applicable).
  • Screenshots or videos demonstrating the problem.

-# ➜ Need to contact support? Visit the OpenAI Help Center.