Codex app cross-thread messaging still uses removed dynamic tools #44871

Activity

1. Serma2019

   added

   appIssues related to the Codex desktop appIssues related to the Codex desktop app

   on Sep 11, 2026
2. github-actions

   added

   bugSomething isn't workingSomething isn't working

   app-serverIssues involving app server protocol or interfacesIssues involving app server protocol or interfaces

   mcpIssues related to the use of model context protocol (MCP) serversIssues related to the use of model context protocol (MCP) servers

   subagentIssues involving subagents or multi-agent featuresIssues involving subagents or multi-agent features

   remote

   windows-osIssues related to Codex on Windows systemsIssues related to Codex on Windows systems

   on Sep 11, 2026
3. Stix01 commented on Sep 12, 2026

   

   Stix01

   on Sep 12, 2026

   Last edited by Stix01

   More actions

   I’ve consolidated my reproduction, clean-runtime test results, and desktop routing findings in the existing headless-host report: diagnostic comment on #42973.
4. yjy0701 commented on Sep 23, 2026

   

   yjy0701

   on Sep 23, 2026 – with ChatGPT Codex Connector

   More actions

   Additional reproduction on 2026-09-23, reported with the affected user's permission.

   This also occurs in a Codex desktop task using a local Windows workspace (not a Remote SSH workspace in this reproduction).

   Observed:

   • The model-visible dynamic tool catalog still advertises codex_app__send_message_to_thread and codex_app__wait_threads with their argument schemas.
   • An explicitly authorized send to an existing task returns the rejection below. Read-only wait_threads with timeoutMs: 0 for the same existing task returns the same rejection.
   • Repeated checks in subsequent turns reproduce it.
   • No callable codex_app MCP replacement for these thread operations is exposed in the available tool catalog. Other tools, including local file reads and the GitHub connector used to submit this report, remain usable.

   Exact rejection:

   This app tool is no longer available through dynamic tools. Use the codex_app MCP server. If that server is unavailable on this host, task delegation is unavailable.
   

   Reproduction:

   1. In an existing Windows desktop task, ask Codex to inspect or send an authorized follow-up to another existing task.
   2. Discover the advertised thread tools.
   3. Call codex_app__wait_threads with a valid existing task ID and timeoutMs: 0, or call the authorized codex_app__send_message_to_thread.
   4. Observe the migration rejection, with no callable replacement available.

   Expected: provide the replacement before retiring the advertised route, or return an actionable capability diagnostic/recovery procedure. Existing-task status checks and authorized handoffs should remain available.

   Impact: the coordinating task cannot inspect the development task or deliver a prepared follow-up; the user must manually relay it.

   Limits: no confirmed root cause, triggering version, or successful restart/update remediation is claimed here. The exact About-dialog app/runtime versions were not collected for this report. No task IDs, project names/paths, conversation transcripts, screenshots, business data, credentials, or raw logs are included. Please clarify the supported way to restore the first-party codex_app bridge for affected existing local Windows tasks.
5. thunderhog commented on Sep 23, 2026

   

   thunderhog

   on Sep 23, 2026 – with ChatGPT Codex Connector

   More actions

   Additional local-Windows reproduction on 2026-09-23. The affected user explicitly requested that this be reported.

   In a Codex desktop task, the model-visible catalog advertises codex_app__list_threads and codex_app__send_message_to_thread, but calling list_threads returns:

   This app tool is no longer available through dynamic tools. Use the codex_app MCP server. If that server is unavailable on this host, task delegation is unavailable.
   

   The documented replacement is not usable in this session either: an explicit MCP resource-list request to server: "codex_app" fails during startup with:

   MCP startup failed: handshaking with MCP server failed: connection closed: initialize response
   

   Thus the catalog advertises legacy tools that reject calls while the instructed MCP route fails initialization. The user reports that app updates/restarts and a computer restart have not restored inter-task communication. No message was delivered to another task. Please provide a supported recovery path for existing desktop tasks and ensure tool discovery reflects the callable surface.

   No task IDs, private paths, project data, credentials, transcripts, or raw logs are included.