Codex Desktop 0.144.5 does not mount installed Slack or Outlook connector tools

What version of Codex is running?

codex-cli 0.144.5, bundled with Codex Desktop build 26.707.91948.

Known-good comparison: cached Codex Desktop build 26.623.31921 with CLI 0.142.2.

What subscription do you have?

ChatGPT Pro.

Which model were you using?

gpt-5.6-sol

What platform is your computer?

Apple Silicon macOS: Darwin 25.5.0 arm64 (Mac OS 26.5.2).

What terminal are you using?

Codex Desktop. The connector health comparison was also run through the bundled CLI.

Codex doctor report

The full report was uploaded with /feedback under diagnostic thread 019f6b25-8a90-7541-a689-447824491648.

Relevant results:

• Codex version 0.144.5
• ChatGPT auth configured successfully
• apps, plugins, remote_plugin, mentions_v2, and tool_suggest enabled
• tool_search_always_defer_mcp_tools enabled
• tool_search removed/disabled

The report's network failures occurred because codex doctor was run in a restricted diagnostic shell. They are not the connector failure: /feedback uploaded successfully, and current Slack and Outlook credentials work through CLI 0.142.2.

What issue are you seeing?

Codex Desktop advertises the installed Slack and Outlook Email plugins but does not mount either connector's callable tools for the model.

In failing turns:

• codex_apps starts and lists 192 cached app tools.
• Slack and Outlook Email remain installed, enabled, linked, and present in the app-tool cache.
• The model-visible dynamic tool set contains only codex_app and plugin_management.
• No Slack or Outlook namespace is mounted.
• tool_search is also absent, so the model cannot discover deferred connector tools.
• No connector tool call occurs.
• No Slack/Microsoft 401, 403, OAuth, or API error occurs.
• Plugin mentions can arrive as plain text, and one affected task recorded selected_capability_root_count=0.

This affects both fresh and resumed Codex Desktop tasks. A task that successfully called Outlook under CLI 0.144.2 lost Outlook, Slack, tool_search, and unrelated dynamic task tools after being resumed under CLI 0.144.5.

This appears related to deferred-tool exposure, but it is not the same symptom as #24536. That issue has tool_search present and concerns an empty codex exec completion. Here, current Desktop tasks do not expose tool_search or the connector tools at all.

Steps to reproduce

1. Install and enable the curated Slack and Outlook Email plugins in Codex Desktop.
2. Link valid Slack and Microsoft accounts.
3. Start a new Codex Desktop task under build 26.707.91948 / CLI 0.144.5.
4. Mention the Slack and Outlook Email plugins and request:

• A Slack public-message search using an arbitrary benign query
• Outlook Email get_profile()

1. Observe that neither connector tool is available to the model.
2. Inspect the task log:

• codex_apps starts and loads the cached tools.
• The dynamic schema does not expose Slack, Outlook, or tool_search.
• No provider call or provider authentication error occurs.

1. Run the same read-only requests through cached CLI 0.142.2 with the same current auth and plugin state.
2. Observe both calls complete successfully.

What did you expect to happen?

Installed, enabled, and linked connector tools should be callable in both new and resumed Desktop tasks.

If connector tools are deferred, Codex must expose a working discovery/execution surface such as tool_search. Plugin mentions should preserve capability metadata and select the requested capability roots.

Additional information

Read-only live verification with the current connector credentials and cached CLI 0.142.2:

• A Slack public-message search completed successfully with no error.
• Outlook Email get_profile() completed successfully with no error.

This isolates the regression to current Codex dynamic-tool assembly rather than Slack, Microsoft, OAuth, plugin metadata, or the linked accounts.

Slack initially lacked a persistent enabled-plugin stanza. Installing/enabling it fixed that separate configuration problem, but did not restore callable Slack or Outlook tools under CLI 0.144.5.

Expected product behavior:

• Rebuild dynamic tool schemas on every new and resumed turn.
• Do not reuse a stale tool snapshot across runtime/protocol upgrades.
• Preserve plugin mention metadata through submission and capability-root selection.
• Never defer app tools without exposing a working discovery/execution path.