›_ Codex Issues
Codex Issues / #40921

open the old chat

Resolved 💬 3 comments Opened Aug 26, 2026 by reza18s Closed Aug 26, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the Codex App are you using (From “About Codex” dialog)?

latest

What subscription do you have?

plus

What platform is your computer?

windos

What issue are you seeing?

ChatGPT can't load config.toml, so this thread can't resume.
Fix config.toml: invalid transport
in mcp_servers.codex_app
. After saving the file, reopen the thread.

What steps can reproduce the bug?

opning the old chats

What is the expected behavior?

_No response_

Additional information

<img width="1280" height="820" alt="Image" src="https://github.com/user-attachments/assets/7a1ec08b-5be6-40db-a303-34a8bba3a596" />

View original on GitHub ↗

3 Comments

taobaibais · 1 day ago

This appears to be the same ongoing mcp_servers.codex_app regression affecting many Windows/WSL users. Could OpenAI please acknowledge the incident publicly? There are already multiple detailed reports and confirmations, but affected users still have no visible maintainer status on whether a fix or rollback is in progress.

github-actions[bot] contributor · 1 day ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #40910
  • #40819
  • #40860
  • #40715
  • #40881

Powered by Codex Action

cpl366 · 1 day ago

If this started after the 26.820.x Windows update and your Codex Desktop is configured to run the agent in WSL, this error is very likely not coming from your own config.toml.

There are now several matching reports (#40910, #40819, #40881, #40715) showing that Desktop can inject an internal mcp_servers.codex_app entry without a valid transport on the WSL path.

A useful A/B test / temporary workaround is:

  1. Back up your current config.toml.
  2. Change only the Desktop WSL setting to:
[desktop]
runCodexInWindowsSubsystemForLinux = false
  1. Fully exit Codex Desktop (including tray/background process) and reopen it.
  2. Try the old chat again.

If it resumes, that strongly isolates this to the Desktop -> WSL runtime-injected MCP regression rather than a damaged thread or user config.

Important: this moves execution back to native Windows, so it is only a temporary workaround if your projects/toolchain depend on WSL. I would not delete the old chat, clear .codex, or rewrite session JSONL files for this error.