[Bug]: Codex websocket fails with 403 Forbidden after upgrading to 0.0.25-nightly.20260603.445

[putueddy]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop (Codex provider)

Summary

Immediately after upgrading to 0.0.25-nightly.20260603.445, an error toast
appears reporting that the Codex responses websocket fails to connect with
HTTP 403 Forbidden:

2026-06-03T04:59:43.895480Z ERROR codex_api::endpoint::responses_websocket: failed to connect to
websocket: HTTP error: 403 Forbidden, url: wss://chatgpt.com/backend-api/codex/responses

This is a 403 Forbidden, not the previously reported 401 Unauthorized (#2797)
or the CA-cert / SSE-fallback case (#765), so it appears to be a distinct
regression that started with this nightly build.

Steps to reproduce

1. Upgrade T3 Code to 0.0.25-nightly.20260603.445.
2. Use the Codex provider (signed in with a ChatGPT/Codex account).
3. Start a thread / send a prompt.
4. The error toast above appears as Codex tries to open the responses websocket.

Expected behavior

The Codex responses websocket connects successfully, or the client falls back
gracefully without surfacing a blocking error toast.

Actual behavior

The websocket connection is rejected with HTTP 403 Forbidden and an error
toast is shown.

Version or commit

0.0.25-nightly.20260603.445

Environment

• Arch Linux
• Codex provider authenticated via ChatGPT account

Logs or stack traces

2026-06-03T04:59:43.895480Z ERROR codex_api::endpoint::responses_websocket: failed to connect to
websocket: HTTP error: 403 Forbidden, url: wss://chatgpt.com/backend-api/codex/responses