openai / openai/codex

Codex Desktop Windows: cannot start chat — invalid transport in mcp_servers.codex_app

Open
#46,342 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app app-server bug mcp windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

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

26.911.61220

What subscription do you have?

ChatGPT Business

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Codex Desktop cannot start any local chat on native Windows.

Exact error:
failed to load configuration: invalid transport in mcp_servers.codex_app

The failure occurs before the chat starts and before any command can run.

Diagnostic logs repeatedly show:
failureReason=invalid_config
method=thread/start
failed to load configuration: invalid transport in mcp_servers.codex_app

codex-cli version: 0.155.0-alpha.2.6

I checked ~/.codex/config.toml and there is no [mcp_servers.codex_app] section. No explicit WSL configuration was found. Codex is running natively on Windows.

Repairing/reinstalling Codex Workspace dependencies and checking for application updates did not resolve the issue.

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a0b224-2c51-7791-b8fa-7f063a95ca4f

What is the expected behavior?

Codex should successfully start the local chat/thread and execute the requested commands in the selected local repository without a configuration error.

Additional information

The issue has reproduced repeatedly across multiple attempts.

Codex Desktop version: 26.911.61220
codex-cli version: 0.155.0-alpha.2.6
Subscription: ChatGPT Business
Environment: native Windows, not WSL.

The user config.toml does not contain an [mcp_servers.codex_app] entry, but the error references mcp_servers.codex_app during thread/start.

No project files are modified because the failure occurs before the thread starts.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the native Windows startup failure and tracing configuration loading during thread/start, especially the unexpected mcp_servers.codex_app entry. Compare the loaded configuration with ~/.codex/config.toml, which lacks that section. Done means Codex Desktop starts a local chat and executes commands without the invalid-transport error.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, desktop-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.