›_ Codex Issues
Codex Issues / #33654

Codex app thread-management tools are no longer exposed to agents after update

Resolved 💬 2 comments Opened Jul 16, 2026 by PurpleDevX Closed Jul 17, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.707.91948

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

After updating the Codex desktop app, the agent-facing thread-management tools are missing from the tool registry.

My workflows make heavy use of these thread tools for orchestration, and this is blocking development of half of my projects.

Previously, agents could use tools such as:

  • create_thread
  • read_thread
  • list_threads
  • send_message_to_thread
  • fork_thread
  • handoff_thread
  • set_thread_title
  • set_thread_pinned
  • set_thread_archived

In a new session after the update, none of these tools are available. Only limited Codex app tools such as terminal reading, workspace dependency loading, and page navigation are exposed.

What steps can reproduce the bug?

  1. Update the Codex desktop app to the latest version.
  2. Start a new Codex task.
  3. Ask the agent to list its available tools or perform a task that requires creating and managing another Codex task.
  4. Observe that the thread-management tools are absent.

What is the expected behavior?

The Codex app should expose its supported thread-management tools to the agent, including tools for creating, listing, reading, messaging, and managing tasks.

Additional information

The current official Codex documentation still describes tasks, agent threads, and parallel-agent management. I could not find a release note announcing removal of these capabilities.

Restarting the app and creating a new task did not restore the missing tools.

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 1 month ago

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

  • #33598
  • #33585
  • #33637

Powered by Codex Action

rcawston · 1 month ago

Confirming that the related bug still occurs on the latest officially available Codex Desktop release for macOS:

  • Codex Desktop: 26.715.31251 (build 5538)
  • Bundled CLI: codex-cli 0.145.0-alpha.18
  • Platform: Darwin 25.4.0 arm64 arm
  • Subscription: Pro

After a full app restart, an affected long-lived local Desktop task still has none of the first-class task-management tools. Its persisted dynamic-tool manifest contains only:

automation_update
read_thread_terminal
load_workspace_dependencies

The post-restart startup log explicitly lists thread_tools as enabled, but resuming the affected task does not rebuild its manifest. A brand-new local task created under the same app process receives all ten task tools, and a read-only list_threads({ "limit": 1 }) call succeeds.

This means the latest build can still leave existing tasks permanently degraded even after restart and feature re-enable. Fresh-task creation is healthy in this instance; existing-task dynamic-tool rehydration is not.

Detailed sanitized evidence and the feature-gate mapping are in #33947.