-
Notifications
You must be signed in to change notification settings - Fork 941
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/web
Steps to reproduce
- Start T3 Code and open a normal Codex thread.
- Make sure the app is working normally first.
- Disconnect the machine from the internet completely.
- Go back to T3 Code and try to continue using the thread.
- Watch the UI state in the thread view and sidebar.
This was not a server-down case for me. I was literally offline, and the app did not make that obvious.
Expected behavior
The UI should show a clear offline / no-connection state when internet connectivity drops or when the app cannot reach the provider reliably.
At minimum, I should get an obvious warning that the app is disconnected or offline, instead of having to guess whether Codex is still reachable.
Actual behavior
When I lost internet, the app did not clearly tell me I was offline.
From the UI, it was not obvious that there was no connection. I had to infer it from the fact that things were not progressing. The missing part here is the user-facing status/warning, not just reconnect behavior under the hood.
Impact
Major degradation or frequent failure
Version or commit
main @ 9e29c9d
Environment
WSL2 (Ubuntu) with Windows 11, t3 code via npx
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
Only manual checking so far: verify internet separately, then retry/restart once connectivity is back.
I did not find a real in-app workaround that clearly surfaced the problem.