Skip to content

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

Open
Open
Codex Desktop 0.144.5 does not mount installed Slack or Outlook connector tools#33601
Labels
appIssues related to the Codex desktop appbugSomething isn't workingskillsIssues related to skillstool-callsIssues related to tool calling

Description

@sudoconnor
sudoconnor
opened on Jul 16, 2026

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()
  5. Observe that neither connector tool is available to the model.
  6. 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.
  7. Run the same read-only requests through cached CLI 0.142.2 with the same current auth and plugin state.
  8. 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.

Activity

  1. github-actions
    added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    skillsIssues related to skills
    tool-callsIssues related to tool calling
    on Jul 16, 2026

  2. github-actions commented on Jul 16, 2026

    @github-actions
    github-actionsBot
    on Jul 16, 2026 – with GitHub Actions
    Contributor

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

    Powered by Codex Action

  3. KalleChen commented on Aug 8, 2026

    @KalleChen
    KalleChen
    on Aug 8, 2026

    Reproduced on ChatGPT Desktop build 26.803.41515 with bundled codex-cli 0.147.0-alpha.6.5. Slack plugin 0.1.6 is installed, enabled, and linked. A fresh task launched via “Try now” exposes neither Slack tools nor tool_search.

  4. Farzan-Memarian-NV commented on Aug 11, 2026

    @Farzan-Memarian-NV
    Farzan-Memarian-NV
    on Aug 11, 2026

    Confirmed on ChatGPT Desktop 26.803.41515 (CFBundleVersion 6321) with stable codex-cli 0.147.0, running macOS 26.5.2 (25F84) on Apple Silicon.

    The Slack connection itself appears healthy:

    • Slack is installed and enabled.
    • Workspace app inventory reports Slack as available, not disabled by an administrator, with an existing OAuth link.
    • Host-side codex doctor --summary reports ChatGPT authentication configured, MCP healthy, WebSocket connected (HTTP 101), and provider endpoints reachable.
    • The same Slack connection works in regular ChatGPT Chat.

    In the affected Codex task, explicitly invoking @Slack loads the Slack skill but does not expose any callable Slack tools. The model-visible catalog lacks:

    • slack_read_user_profile
    • slack_search_channels
    • slack_read_channel
    • slack_read_thread
    • tool_search

    Consequently, no Slack API request occurs and there is no 401, 403, or OAuth error to diagnose. Reconnecting Slack, reinstalling/re-enabling the plugin, and starting new tasks have not resolved it. Slack also remains unavailable in ChatGPT Work.

    This looks like the same dynamic tool-mounting/capability-root regression, now reproduced with stable codex-cli 0.147.0, rather than an account authorization or network issue.

  5. kasimiamohea-commits commented on Sep 24, 2026

    @kasimiamohea-commits
    kasimiamohea-commits
    on Sep 24, 2026

    Additional reproduction on current Windows build: Gmail and Slack connector tools are not exposed

    This appears to be the same tool-exposure symptom as #33601 and is provided as additional current-build evidence rather than a duplicate issue.

    Environment

    • Codex Desktop conversation on Windows
    • codex-cli 0.155.0-alpha.16.4
    • Windows NT 10.0.26200.0
    • Gmail and Slack plugins are displayed as connected in the Codex UI
    • The same account can use Gmail and Slack read/search/send tools from ChatGPT

    Reproduction

    1. Open a Codex conversation with the Gmail and Slack plugins connected.
    2. Ask Codex to use a Gmail read/search/send operation or a Slack channel search/read/send operation.
    3. Inspect the callable tools available to the conversation.
    4. Repeat the same check after confirming that the plugins remain connected in the UI.

    Actual behavior

    • Gmail is recognized, but no Gmail callable tools are exposed.
    • gmailTools: []
    • Slack is recognized, but no Slack callable tools are exposed.
    • slack tools: []
    • tool_search is not present in the conversation.
    • Plugin search/status tools are absent.
    • resources: [] and resourceTemplates: [] were also observed, but these are included only as observations and are not the primary failure evidence.
    • No Gmail or Slack tool call can be attempted.
    • No Gmail API error, Slack API error, OAuth error, 401, or 403 is produced, because the tool itself is not present in the conversation.

    The primary failure occurs before a provider request. It is therefore not currently reproducible as a Gmail or Slack API failure.

    Control comparison

    The Superpowers plugin is recognized successfully:

    • The plugin/skill package is visible.
    • The skill list is available.
    • The TDD skill body can be read.
    • The skill content can be used in the response.
    • No Superpowers-specific MCP tool is required.

    This indicates that plugin/skill package injection and built-in tools are working, while MCP-backed external callable tools are missing.

    Surface UI/plugin recognized Callable tools exposed Result
    Gmail Yes No (gmailTools: []) Cannot call read/search/send
    Slack Yes No (slack tools: []) Cannot call search/read/send
    Superpowers Yes Not applicable Skills load and work
    ChatGPT Gmail/Slack Yes Yes Same account can call the connectors

    Expected behavior

    When a connected Gmail or Slack plugin is available, Codex should expose the connector tools to the conversation, or provide a clear discovery/authorization path. If tools are deferred, a working tool_search or equivalent discovery mechanism must be available.

    Additional context

    The observed failure is shared by two different external services, while ChatGPT can call both services normally. The current evidence points to a Codex-side tool exposure/injection boundary. Possible areas for investigation include codex_apps, MCP connector discovery, session tool injection, and deferred external-tool exposure, but these are hypotheses rather than confirmed causes.

    Related reports: #33601, #33571, #33609, #19425. This report does not include connector contents, OAuth tokens, cookies, account identifiers, or personal data.

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 appbugSomething isn't workingskillsIssues related to skillstool-callsIssues related to tool calling

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions