Before submitting
Area
apps/web
Steps to reproduce
Open t3code in a browser using the remote/web setup.
Connect from a mobile device or tethered connection with ~100–200ms ping.
Start a thread and send a message.
Observe the connection status bar — the client repeatedly disconnects and reconnects.
Try to load an existing thread or send a follow-up after a reconnect.
Expected behavior
The app should handle transient network interruptions gracefully. Brief disconnections on a high-latency mobile link should not cause visible spam or broken state. Threads should reload cleanly after reconnection, and the session should resume without desync.
Actual behavior
On a mobile connection with 100–200ms ping:
The UI gets spammed with repeated "Disconnected from" toasts followed by immediate reconnection attempts in a continuous loop. Some threads refuse to load after a reconnect — staying blank or showing stale content. Threads also become desynced: local and server state diverge, and sending new messages silently fails or the message does not appear. The app is effectively unusable on any connection with moderate latency or packet loss.
Impact
Blocks work completely
Version or commit
No response
Environment
Browser (web/remote setup), mobile connection (4G/LTE), ~100–200ms ping
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
None found. Staying on a stable Wi-Fi connection avoids the issue entirely, but there is no way to recover a desynced thread mid-session without reloading the page.
Before submitting
Area
apps/web
Steps to reproduce
Open t3code in a browser using the remote/web setup.
Connect from a mobile device or tethered connection with ~100–200ms ping.
Start a thread and send a message.
Observe the connection status bar — the client repeatedly disconnects and reconnects.
Try to load an existing thread or send a follow-up after a reconnect.
Expected behavior
The app should handle transient network interruptions gracefully. Brief disconnections on a high-latency mobile link should not cause visible spam or broken state. Threads should reload cleanly after reconnection, and the session should resume without desync.
Actual behavior
On a mobile connection with 100–200ms ping:
The UI gets spammed with repeated "Disconnected from" toasts followed by immediate reconnection attempts in a continuous loop. Some threads refuse to load after a reconnect — staying blank or showing stale content. Threads also become desynced: local and server state diverge, and sending new messages silently fails or the message does not appear. The app is effectively unusable on any connection with moderate latency or packet loss.
Impact
Blocks work completely
Version or commit
No response
Environment
Browser (web/remote setup), mobile connection (4G/LTE), ~100–200ms ping
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
None found. Staying on a stable Wi-Fi connection avoids the issue entirely, but there is no way to recover a desynced thread mid-session without reloading the page.