Slack plugin is selected but Slack tools are unavailable in Codex desktop sessions

Open
#33,676 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop

Research direction

Reproduce the failure from the Plugins directory by selecting @Slack in a new Codex desktop session, then request messages from an authorized channel. Compare the selected plugin with the session's available tools and verify whether Slack read tools are provisioned; done means the authorized channel messages and threads can be read without modifying Slack.

Written by the indexing model from the issue text.

Description

app bug skills tool-calls
What version of the Codex App are you using (From “About Codex” dialog)?

26.707.91948

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

The Slack plugin can be installed and explicitly selected with @Slack, but the Slack read and write tools are not provisioned in the Codex desktop session.

Slack works correctly in ChatGPT Work on the web using the same OpenAI account, Slack workspace, connector, and permissions. The problem only occurs in the desktop application and started on July 16, 2026. The same Slack workflow worked correctly in the desktop application approximately two days earlier.

When I ask Codex to read a Slack channel, it returns the following message:

Original message:

No pude leer el canal porque las herramientas de acceso a Slack no están disponibles en esta sesión, aunque el plugin aparece seleccionado. No publiqué ni modifiqué nada. Reconecta Slack o abre una sesión donde el conector esté habilitado y lo revisaré.

English translation:

I could not read the channel because the Slack access tools are not available in this session, even though the plugin is selected. I did not publish or modify anything. Reconnect Slack or open a session where the connector is enabled, and I will review it.

The Slack channel identifier and workspace information have been redacted because this is a public issue.

I have already completed the following troubleshooting:

  • Created multiple new sessions.
  • Tested in both Chat and Work modes.
  • Explicitly selected the Slack plugin using @Slack.
  • Signed out of the desktop application and signed back in.
  • Completely closed and restarted the application.
  • Removed and reinstalled the Slack plugin.
  • Revoked and reauthorized the Slack connection.
  • Removed and reinstalled the desktop application.
  • Removed and reinstalled the Slack-side authorization.
  • Confirmed that Slack continues to work in ChatGPT Work on the web.

The issue persists after all of these steps.

An in-app feedback attempt generated this identifier:

no-active-thread-019f6c5f-a7b3-7472-9a28-f07a837baed4

The feedback interface did not provide an option to include or share the active conversation.

What steps can reproduce the bug?
  1. Open the Codex/ChatGPT desktop application.

  2. Sign in with the same ChatGPT account used on ChatGPT Work on the web.

  3. Open the Plugins directory.

  4. Install the official Slack plugin.

  5. Connect and authorize an existing Slack workspace.

  6. Create a completely new desktop session.

  7. Type @Slack and explicitly select the Slack plugin.

  8. Enter the following prompt, using an authorized Slack channel:

    Read the messages and threads from the last hour in Slack channel [REDACTED_CHANNEL_ID]. Do not publish or modify anything.

  9. Submit the prompt.

  10. Codex reports that the Slack access tools are unavailable in the session, even though the Slack plugin is visibly selected.

Expected behavior:

Codex should load the Slack read tools into the session and retrieve the authorized channel messages and threads without publishing or modifying anything.

Actual behavior:

The Slack plugin is selected, but no Slack tools are available to the session. Codex cannot read the channel and recommends reconnecting Slack. Reconnecting, reinstalling, and reauthorizing do not resolve the issue.

Frequency:

The issue occurs every time in every newly created desktop session tested since July 16, 2026.

What is the expected behavior?

No response

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.