[Windows Desktop] create_thread absent from tool manifest in a task that instructs agents to use it #46147

Activity

1. github-actions

   added

   bugSomething isn't workingSomething isn't working

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

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

   sessionIssues involving session (thread) management, resuming, forking, naming, archivingIssues involving session (thread) management, resuming, forking, naming, archiving

   on Sep 17, 2026
2. github-actions commented on Sep 17, 2026

   

   github-actionsBot

   on Sep 17, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Windows Desktop: native cross-task tools missing from an existing local task #45166

   Powered by Codex Action
3. eagl3r0yal commented on Sep 22, 2026

   

   eagl3r0yal

   on Sep 22, 2026 – with ChatGPT Codex Connector

   More actions

   Additional reproduction on Windows, observed on September 22, 2026.

   The affected user explicitly requested escalation and reports that this workflow previously worked, but has been unavailable for approximately two weeks across multiple separately opened sessions. Starting another session has therefore not resolved it for this user. The exact last working build and regression date are unknown.

   Verified in the current Desktop task:

   • The user explicitly asked the agent to create a clean, separate user-facing task with a handoff.
   • The app-provided instructions refer to native task-management tools.
   • Enumeration of the complete model-visible callable tool catalog returned no create_thread, fork_thread, list_threads, or read_thread.
   • No additional tool-discovery capability capable of exposing these operations is available in this session.
   • Other capabilities, including shell execution and connected app tools, work.
   • No creation call could be made. This is tool absence, not an approval rejection or a tool handler error.
   • The local standalone CLI reports codex-cli 0.153.4; this is NOT asserted to be the Desktop app or bundled runtime version. The Desktop build was not established.
   • Environment: Windows, PowerShell, filesystem-backed project workspace. Local model configuration selects gpt-6-astra; no controlled model comparison was performed.
   • No configuration change, app restart, raw state-database modification, or CLI-created substitute task was performed as part of the diagnostic.

   Impact: the user must manually move prepared handoffs between tasks or keep working in the same task. This repeatedly interrupts a long-running project workflow. A subagent is not a replacement for the requested user-owned sidebar task.

   Please investigate why the task-management tool family is omitted across fresh sessions, restore the supported workflow, or expose an actionable reason when unavailable. The user reports a persistent multi-session regression; suggesting another new session alone does not address the observed experience.

   This report intentionally contains only the relevant technical observations, without project files, private conversation contents, credentials, local account paths, or session identifiers.

   👀React with 👀1Reacted by The G
4. gitmengzh commented on Sep 23, 2026

   

   gitmengzh

   on Sep 23, 2026 – with ChatGPT Codex Connector

   Last edited by gitmengzh

   More actions

   Additional Windows reproduction on 2026-09-24:

   • Installed Desktop package: OpenAI.Codex 26.917.8451.0 (Windows package metadata).
   • In an existing local project task, app instructions explicitly direct the agent to use create_thread when the user requests a new task.
   • The user explicitly requested a new project task. The model-visible catalog contains 232 tools, but exact-name checks found no create_thread, fork_thread, or send_message_to_thread; broader thread/task-management tool search also found no replacement.
   • This is absence from the callable catalog, not an invocation failure or approval denial. Ordinary file and shell tools still work.
   • The user reports this workflow worked previously. I have not isolated whether the package update, task restoration, feature gating, or runtime configuration caused the loss.

   Expected: expose the task-management tools when the app instructs agents to use them, or surface a specific diagnostic and recovery path. No private paths, task IDs, logs, credentials, or conversation content are attached.
5. b4rlw commented on Sep 24, 2026

   

   b4rlw

   on Sep 24, 2026

   More actions

   I've also started seeing lots of failures like this:
   "I can’t spawn the new Codex task from this session because the create_thread tool isn’t available here."

   👍React with 👍2Reacted by wjlevan1 and Miguel Sánchez Villafán