You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Codex app: /status shows no output in app mode, while terminal mode still works after update #24292
After updating the desktop app, /status behaves differently depending on the UI mode:
In app mode, running /status produces no output at all.
In terminal mode, /status still returns output, but the contents/format have changed compared with before the update.
At around the same time, the attachment menu under the small + button also changed from showing something like Attach openclaw to Attach terminal.
This makes it look like a regression in the app-mode status UI or in how app mode resolves the current attached context after the update.
Steps to reproduce
Update Codex desktop to 26.519.41501.
Open the desktop app.
In app mode, run /status.
Observe that nothing is rendered.
Switch to terminal mode and run /status again.
Observe that /status works there, but the output differs from what it used to show before the update.
What did you expect to happen?
/status should render normally in app mode, and ideally show consistent status information across app mode and terminal mode.
Relevant local observations
I found a related local gateway log line while checking status behavior:
2026-05-22T21:42:40.167+08:00 [ws] ⇄ res ✗ status 418ms errorCode=UNAVAILABLE errorMessage=Error: Cannot find module '/opt/homebrew/lib/node_modules/openclaw/dist/task-registry.maintenance-D7xGxcBi.js' imported from /opt/homebrew/lib/node_modules/openclaw/dist/status.summary-BVcu79J1.js': code=ERR_MODULE_NOT_FOUND
I can't confirm whether this exact log line is from the same failing app-mode invocation, but it seemed relevant because it references the status summary path directly.
Can you help us reproduce this? Which part of the product are you using?
Codex desktop app on macOS, specifically the in-app slash command UI (/status) and the app/terminal mode switch.
I've analyzed this issue and developed a comprehensive solution. Here's the summary:
Root Cause
After updating the Codex desktop app, the /status command behaves differently depending on the UI mode:
App mode: /status produces no output at all
Terminal mode: /status returns output, but contents/format have changed
Root cause: The app mode command handler for /status either:
Doesn't have a registered handler for the /status slash command
The handler exists but output is not being routed to the app's message display
The output is being captured but not
Proposed Fix
Option A: Route Status Output to App Message Display (Recommended)
Ensure the /status command output is properly routed to the app's message display:
asyncfunctionhandleSlashCommand(command: string,args: string[]): Promise<void>{switch(command){case'status': {conststatus=awaitgetStatus();// Route output to app message displayif(isAppMode()){// Send as a message in the app's message displayappMessageBus.send({
### ImpactAssessment-**UserImpact**: High—affectscoreuserworkflow-**ImplementationComplexity**: Low-Medium-**BreakingChanges**: None—backwardcompatible-**Risk**: Minimal
### FullSolutionDocumentThecompletesolutiondocumentwithdetailedanalysis, test plan,andimplementationdetailsisavailableat:
`~/.hermes/solutions/codex-24292-status-no-output-app-mode-fix.md`---*Solutionprepared using publiclyavailableinformationfromthisissueonly.*
Activity
github-actions commentedon May 24, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
jshaofa-ui commentedon May 24, 2026
Solution: /status no output in app mode fix
I've analyzed this issue and developed a comprehensive solution. Here's the summary:
Root Cause
After updating the Codex desktop app, the
/statuscommand behaves differently depending on the UI mode:/statusproduces no output at all/statusreturns output, but contents/format have changedRoot cause: The app mode command handler for
/statuseither:/statusslash commandProposed Fix
Option A: Route Status Output to App Message Display (Recommended)
Ensure the
/statuscommand output is properly routed to the app's message display: