ChatGPT desktop repeatedly loses bundled Codex app-server after workspace auth 401; in-app feedback also fails
Summary
The ChatGPT desktop app on macOS repeatedly enters the "ChatGPT unexpectedly stopped" recovery screen because the bundled Codex app-server becomes unresponsive and is then terminated with SIGKILL. In-app feedback upload also fails.
Feedback ID from the failed upload: 019f21b4-19d1-75c1-baac-7d2b9210925e
Environment
- macOS 26.5.1 (25F80)
- ChatGPT desktop app: 26.818.41509 (bundle build 6962)
- Bundled Codex CLI: 0.149.0-alpha.4.1
- Authentication method: ChatGPT
Reproduction
- Launch the ChatGPT desktop app.
- Open or create a local Codex task.
- Submit a prompt or leave the app running for several minutes.
- The app-server stops responding, requests time out, and the app displays "ChatGPT unexpectedly stopped."
- Restarting temporarily recovers the app, but the problem repeats.
- Attempting to submit in-app feedback displays "Feedback upload failed" while preserving the feedback ID above.
Relevant sanitized log sequence
sa_server_request_failed status=401 errorMessage={"detail":"Must use workspace account for this operation"}
Thread catalog sync failed errorMessage="App server account changed"
mcp_request_timeout method=turn/start timeoutMs=30000
app_server_connection.closed signal=SIGKILL
Codex CLI process exited classifiedAsExpected=false signal=SIGKILL
fatal_error_broadcasted
Request failed errorMessage="Codex app-server is not available"
The account ID, local paths, prompt contents, and full logs have intentionally been omitted.
Troubleshooting already attempted
- Validated
~/.codex/config.tomlsuccessfully. - Disabled ambient suggestions and realtime voice screen context.
- Disabled all plugins and restarted in a clean configuration.
- Moved/rebuilt the Codex and ChatGPT caches.
- Verified the application signature and available disk space.
- Fully restarted the desktop app.
The crash still occurs with all plugins disabled, so it does not appear to be caused by a third-party plugin. The repeated 401/workspace-account-change sequence suggests an authentication or workspace token synchronization loop between the desktop renderer and the bundled app-server.
Expected behavior
The desktop app and bundled app-server should use one stable authenticated principal. A workspace settings 401 should not make the app-server unresponsive or trigger a recurring crash screen, and the feedback uploader should remain usable when reporting the failure.
1 Comment
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action