Slack plugin is selected but Slack tools are unavailable in Codex desktop sessions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
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
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?
-
Open the Codex/ChatGPT desktop application.
-
Sign in with the same ChatGPT account used on ChatGPT Work on the web.
-
Open the Plugins directory.
-
Install the official Slack plugin.
-
Connect and authorize an existing Slack workspace.
-
Create a completely new desktop session.
-
Type
@Slackand explicitly select the Slack plugin. -
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. -
Submit the prompt.
-
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·