Invalid codex_app MCP transport

“failed to load configuration: invalid transport in mcp_servers.codex_app”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/16338/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports in the last two weeks, down from 3 a week at the mid-September peak.

Threads fail to start with invalid transport in mcp_servers.codex_app. Codex Desktop on native Windows reports "failed to load configuration" and existing threads refuse to resume, even with config.toml unedited.

Is this your bug?

File my report

Where: Windows desktop app
Error text: failed to load configuration: invalid transport in `mcp_servers.codex_app`
Versions: 26.911.61220 to 26.915.3509.0
Platforms: Windows
How bad: Stops work: a core feature can't be used. Most reports say it blocks them completely.

Related: Windows app crashes after launch

Not quite your bug?

codex_apps MCP decoding failure18 people
Startup spinner never finishes37 people
Organization settings load failure29 people

Original reports3, newest first

Sep 19, 2026Windows Codex Desktop: recurring invalid transport in mcp_servers.codex_app despite plugin disabledOn GitHub#46598
Sep 18, 2026Codex app writes invalid transport into mcp_servers.codex_app, blocking all threads after restartOn GitHub#46387
Sep 17, 2026Codex Desktop Windows: cannot start chat — invalid transport in mcp_servers.codex_appOn GitHub#46342