【BUG】Slash commands completely not working in Codex Desktop App (no UI + no parsing)

Resolved 💬 9 comments Opened Apr 2, 2026 by Destiny-9527 Closed Apr 15, 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)?

macOS - Codex Desktop App - Tested versions: - codex-cli 0.118.0-alpha.2

What subscription do you have?

plus

What platform is your computer?

macOS

What issue are you seeing?

Summary

Slash commands (/) do not work at all in Codex Desktop App:

No command menu appears when typing /
Commands like /status are not recognized
Input is treated as plain text

This affects both UI and command execution.

---

Environment

macOS
Codex Desktop App
Tested versions:
codex-cli 0.118.0-alpha.2
codex-cli 0.108.0-alpha.12

Additional Context

Other users on the same version (macOS + 0.118.0-alpha.2) can use slash commands normally
Tested with a new account → same issue
CLI works correctly (/status works in codex CLI)

---

Notes

This seems similar to other issues where slash commands:

are ignored or treated as plain text (#3641)
do not trigger in UI (#5114)

However, this case is more severe:

👉 Slash commands are completely non-functional (no UI + no parsing)

---

What steps can reproduce the bug?

Open Codex Desktop App
Start a new thread
Type:/status
Press enter

Actual Behavior

No slash command menu appears
/status is sent as plain text
No command execution happens

Expected Behavior

Typing / should open slash command menu
/status should be recognized and executed

What is the expected behavior?

Possible Cause

Suspected:

Feature flag inconsistency OR
UI regression where slash handler is not registered

---

Impact

Core documented functionality does not work
Inconsistent behavior across users
No fallback or UI hint provided

---

Willing to Help

I can provide:

screen recording
logs (~/Library/Logs/com.openai.codex/)

Additional information

_No response_

View original on GitHub ↗

9 Comments

github-actions[bot] contributor · 3 months ago

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

#16412

Powered by Codex Action

Destiny-9527 · 3 months ago

Additional symptom: when I type /status (or another slash command) and press Enter, the first Enter does nothing at all. Only after pressing Enter a second time is the text sent as a normal chat message. This makes it feel like slash command handling is being intercepted but failing before execution.

tienanh0903k · 3 months ago

Have you been able to fix that problem?

NgdHung31 · 3 months ago

I'm having the same problem on Windows 11, Codex apps 26.325.31654.

I've tried everything including:

Reinstalling Codex apps and restarting my laptop
Logging back into Codex with a different account

I checked the Codex logs and found an authentication issue where requests to "chatgpt.com/backend-api/plugins/*" were blocked. But even after trying the above methods, I'm still being blocked. I'm using a Plus account.

Destiny-9527 · 3 months ago

Have you been able to fix that problem?

test your network connection to ab.chatgpt.com.

Destiny-9527 · 3 months ago

I'm having the same problem on Windows 11, Codex apps 26.325.31654. I've tried everything including: Reinstalling Codex apps and restarting my laptop Logging back into Codex with a different account I checked the Codex logs and found an authentication issue where requests to "chatgpt.com/backend-api/plugins/*" were blocked. But even after trying the above methods, I'm still being blocked. I'm using a Plus account.

test your network connection to ab.chatgpt.com.

NgdHung31 · 3 months ago

> I'm having the same problem on Windows 11, Codex apps 26.325.31654. > I've tried everything including: > > Reinstalling Codex apps and restarting my laptop > Logging back into Codex with a different account > I checked the Codex logs and found an authentication issue where requests to "chatgpt.com/backend-api/plugins/*" were blocked. But even after trying the above methods, I'm still being blocked. I'm using a Plus account. test your network connection to ab.chatgpt.com.

Connectivity to ab.chatgpt.com is working from this environment.

DNS resolves:

172.64.155.209
104.18.32.47
2a06:98c1:3100::6812:202f
2a06:98c1:310b::ac40:9bd1

TCP test to ab.chatgpt.com:443 succeeded, so the host is reachable over HTTPS.

hellooops · 2 months ago

> > I'm having the same problem on Windows 11, Codex apps 26.325.31654. > > I've tried everything including: > > > > Reinstalling Codex apps and restarting my laptop > > Logging back into Codex with a different account > > I checked the Codex logs and found an authentication issue where requests to "chatgpt.com/backend-api/plugins/" were blocked. But even after trying the above methods, I'm still being blocked. I'm using a Plus account. > > > test your network connection to ab.chatgpt.com. Connectivity to ab.chatgpt.com is working from this environment. DNS resolves: 172.64.155.209 104.18.32.47 2a06:98c1:3100::6812:202f * 2a06:98c1:310b::ac40:9bd1 TCP test to ab.chatgpt.com:443 succeeded, so the host is reachable over HTTPS.

I got my slash working after setting a proxy to my codex app and restart.

dproton · 2 months ago

> > > I'm having the same problem on Windows 11, Codex apps 26.325.31654. > > > I've tried everything including: > > > > > > Reinstalling Codex apps and restarting my laptop > > > Logging back into Codex with a different account > > > I checked the Codex logs and found an authentication issue where requests to "chatgpt.com/backend-api/plugins/" were blocked. But even after trying the above methods, I'm still being blocked. I'm using a Plus account. > > > > > > test your network connection to ab.chatgpt.com. > > > Connectivity to ab.chatgpt.com is working from this environment. > DNS resolves: > > 172.64.155.209 > 104.18.32.47 > 2a06:98c1:3100::6812:202f > * 2a06:98c1:310b::ac40:9bd1 > > TCP test to ab.chatgpt.com:443 succeeded, so the host is reachable over HTTPS. I got my slash working after setting a proxy to my codex app and restart.

Could you share the exact steps you took?