Skip to content

Windows Desktop: threads freeze after completion, Send becomes disabled, and mcp_servers.codex_app invalid transport #47013

Open

Description

Summary

I am experiencing multiple recurrent issues in Codex Desktop for Windows that make the app unreliable for sustained work.

Windows app version: 26.915.4065.0

I am using Codex Desktop extensively for project work and Computer Use. The problems occur both inside and outside projects.

There are three distinct failure modes:

1. invalid transport error

Codex intermittently fails with:

failed to load configuration: invalid transport in mcp_servers.codex_app

My user config.toml does NOT contain a [mcp_servers.codex_app] section.

I also verified:

  • No additional *.config.toml profiles exist in %USERPROFILE%.codex
  • No .codex/config.toml exists inside my project (Sirao Estudio)
  • The problem occurs both inside and outside projects

2. Send becomes disabled after a completed turn

A thread works normally and Codex completes its task successfully.

After completion, I can type another message, but:

  • the Send button is disabled
  • pressing Enter does not submit the message
  • the previous task appears completed
  • another/new chat can still work normally

The affected thread becomes effectively unusable.

3. A submitted message runs indefinitely

In other threads, the message is successfully submitted, but the run never completes.

The blue activity indicator keeps spinning indefinitely and the thread remains stuck.

This is different from issue #2 because in this case the message was actually submitted.

Steps already attempted

I have already tried:

  • Full Windows restart
  • New chats
  • Codex Workspace diagnostics: Healthy
  • Reset and install Workspace / Reinstall
  • Windows app Repair
  • Disabling Plugins
  • Disabling codex-app-tools@openai-bundled in config.toml
  • Testing both Windows sandbox modes: elevated and unelevated
  • Checking Microsoft Store for updates
  • Restarting the application
  • Testing inside and outside projects
  • Checking for additional config.toml/profile configuration

Windows Repair temporarily allowed several successful turns, but the problems returned.

Expected behavior

After Codex completes a turn, the same thread should remain usable and allow subsequent messages.

Submitted runs should complete or return an error rather than remaining indefinitely active.

Codex Desktop should not fail because of mcp_servers.codex_app when that MCP server is not defined in the visible user or project configuration.

Actual behavior

Threads intermittently become unusable after one or more successful turns.

Depending on the occurrence:

  • Send becomes disabled after the previous run has completed, OR
  • a submitted run remains indefinitely active, OR
  • Codex reports invalid transport in mcp_servers.codex_app.

Creating a new thread can temporarily work, but this is not a viable workaround for sustained project work.

Feedback / diagnostics

I submitted diagnostics through /feedback with ChatGPT and browser logs enabled.

Feedback ID:

no-active-thread-01a0c3d3-731a-78f2-acdf-89c64b7c8a51

OpenAI Support specifically asked me to file this GitHub issue and include this Feedback ID so the Codex/Windows team can correlate it with the submitted diagnostics.

I can provide additional logs or reproduction information if needed.

Image Image Image

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    mcpIssues related to the use of model context protocol (MCP) servers
    configIssues involving config.toml, config keys, config merging, or config updates
    sessionIssues involving session (thread) management, resuming, forking, naming, archiving
    on Sep 21, 2026
  2. federicoislakoifmann-beep commented on Sep 23, 2026

    @federicoislakoifmann-beep
    Author

    I reproduced the issue again today in a recently created Codex Desktop for Windows conversation.

    The Send button remained blue and appeared enabled, but clicking it did nothing and the message could not be submitted.

    This is not limited to old conversations, and it also occurs outside computer-use/agent workflows.

    I submitted /feedback while the affected chat was still in the broken state, including diagnostic logs.

    Feedback ID: 01a0cb29-010b-77a0-9843-2ebc80a380a7

    This remains reproducible after creating new chats, so starting a fresh conversation is not a reliable workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingconfigIssues involving config.toml, config keys, config merging, or config updatesmcpIssues related to the use of model context protocol (MCP) serverssessionIssues involving session (thread) management, resuming, forking, naming, archivingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions