Environment
- Windows Codex desktop app, version 26.1007.2314.0 (observed in application logs)
- ChatGPT Plus authentication
- Occurred October 10–11, 2026
- Windows system proxy enabled on localhost port 7897; proxy involvement is unconfirmed
Actual behavior
The desktop app repeatedly reports workspace routing discovery failed and Workspace routing is unavailable.
Redacted diagnostic summary from local application logs:
account/read fails with error code -32603 and message workspace routing discovery failed.
- Requests for
/settings/user and /wham/usage report workspace routing unavailable (status 432 in October 10 logs).
- The
hostId=durable WebSocket connection fails with Unexpected server response: 403 and close code 1006.
- Automatic reconnection repeats more than 200 times without becoming ready; logs show reconnectAttempt=201/202 with a 20-second retry delay.
- The current local conversation transcript and working directory both exist, so this occurrence is distinct from a missing local rollout file.
Expected behavior
Account/workspace routing should resolve successfully, or the app should provide an actionable explanation and avoid an indefinite reconnect loop on repeated 403 responses.
Reproduction / limitations
Observed while using an existing desktop conversation and when a scheduled follow-up attempted to run. The issue recurred on consecutive days. No controlled network comparison or sign-out/sign-in test has been completed, so the root cause (network/proxy, authentication, workspace entitlement, or service-side routing) remains unknown.
Please advise which redacted diagnostics would help distinguish these causes. Full transcripts, account identifiers, credentials, and unreviewed logs are intentionally omitted.
Environment
Actual behavior
The desktop app repeatedly reports
workspace routing discovery failedandWorkspace routing is unavailable.Redacted diagnostic summary from local application logs:
account/readfails with error code-32603and messageworkspace routing discovery failed./settings/userand/wham/usagereport workspace routing unavailable (status 432 in October 10 logs).hostId=durableWebSocket connection fails withUnexpected server response: 403and close code 1006.Expected behavior
Account/workspace routing should resolve successfully, or the app should provide an actionable explanation and avoid an indefinite reconnect loop on repeated 403 responses.
Reproduction / limitations
Observed while using an existing desktop conversation and when a scheduled follow-up attempted to run. The issue recurred on consecutive days. No controlled network comparison or sign-out/sign-in test has been completed, so the root cause (network/proxy, authentication, workspace entitlement, or service-side routing) remains unknown.
Please advise which redacted diagnostics would help distinguish these causes. Full transcripts, account identifiers, credentials, and unreviewed logs are intentionally omitted.