Skip to content

codex_app thread tools missing after desktop update to 26.903.8094.0 / codex-cli 0.153.4 (regression of #37075/#30233) #44170

Open

Description

@cryth99

Summary

After the Codex desktop app updated to package OpenAI.Codex_26.903.8094.0 (bundled codex-cli 0.153.4), agent conversations on a custom (non-OpenAI) Responses provider only receive automation_update from the expected 11 codex_app thread tools. A previously verified working state (2026-09-06, codex-cli 0.153.1: 11/11 present, create_thread and list_threads called successfully) regressed after this update.

Environment

Repro

  1. Update the desktop app to the version above.
  2. Start a new conversation (projectless).
  3. Inspect the agent's available function list against the expected 11 codex_app tools.

Result: only automation_update is present. Missing: create_thread, fork_thread, handoff_thread, list_threads, read_thread, send_message_to_thread, set_thread_archived, set_thread_pinned, set_thread_title, wait_threads.

Evidence

  1. The codex app-server process is launched with an inline MCP config whose cwd points inside the signed package:

    C:\Program Files\WindowsApps\OpenAI.Codex_26.903.8094.0_x64__2p2nqsd0c76g0\app\resources\plugins\openai-bundled\plugins\codex-app-tools

    and whose tools map contains only five entries: automation_update, create_thread, send_message_to_thread, fork_thread, handoff_thread.

  2. The internal desktop-mcp.json at that package path confirms only those five tools are listed.

  3. A plugin cache copy at ~/.codex/plugins/cache/openai-bundled/codex-app-tools/0.1.3/desktop-mcp.json lists all 11 tools, but the server is launched from the package path, so the cache copy is bypassed.

  4. App logs show the codex_app MCP server status as ready for the affected thread, so the server starts; the tool set exposed to the agent is still incomplete.

Expected behavior

All 11 codex_app thread tools should be available to agent conversations regardless of provider or app build, consistent with the fix verified for #37075 on codex-cli 0.153.1. If the six list_threads / read_thread / wait_threads / set_thread_* tools were intentionally removed or moved in this build, please document the replacement mechanism.

Suggested fix direction

  • Ensure the app-server launches codex_app MCP from a location that honors the plugin's full tool manifest (or the internal manifest lists all 11 tools), and
  • Re-verify tool injection on custom Responses providers (regression check: 11/11 app tools present).

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
    app-serverIssues involving app server protocol or interfaces
    custom-modelIssues related to custom model providers (including local models)
    on Sep 9, 2026
  2. github-actions commented on Sep 9, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  3. cleacos commented on Sep 17, 2026

    @cleacos

    I miss being able to update the chat title with set_thread_title. I have some scheduled tasks that should update the chat name with the date/time; it worked before, but after that update, the chat title no longer updates.

    It seems those tools exist but aren't exposed.

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 appapp-serverIssues involving app server protocol or interfacesbugSomething isn't workingcustom-modelIssues related to custom model providers (including local models)mcpIssues related to the use of model context protocol (MCP) serverswindows-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