Before submitting
Area
apps/web
Steps to reproduce
- Configure T3 Code with two desktop environments/devices.
- Leave both environments remembered by the client.
- Put one device to sleep (or otherwise make its remote environment unreachable).
- On the online device, open Usage.
- Wait beyond the remote connection timeout.
Expected behavior
The Usage page should eventually show totals from the available environment and clearly mark the offline environment as unavailable/incomplete. A disconnected device should reach a terminal error state or be excluded after a bounded timeout.
Actual behavior
The page remains on its loading skeleton indefinitely with “1 device still scanning.” The online environment completes successfully, while the offline environment is reconnecting and reports a 10-second remote endpoint timeout under Settings → Connections.
The remote usage request appears to remain pending instead of becoming a failure. In the current client flow, useUsage() treats an environment with no summary and no error as still reporting, and UsagePage deliberately holds all content while isPending || isPartial. Because the unreachable environment never becomes terminal, the page never displays even the completed device's totals.
Impact
Major degradation or frequent failure
Version or commit
0.0.34-nightly.20260810.1061
Environment
macOS desktop app; two remembered Mac environments connected using Tailscale HTTPS; one remote Mac asleep/unreachable.
Logs or stack traces
Remote environment endpoint https://<redacted-tailnet-host>/.well-known/t3/environment timed out after 10000ms.
The Connections screen continues showing “Failed to connect. Reconnecting...” / “Connecting...” while Usage remains on “1 device still scanning.”
Workaround
Wake the remote Mac so it reconnects, or temporarily remove the offline environment under Settings → Connections → Remote environments.

Before submitting
Area
apps/web
Steps to reproduce
Expected behavior
The Usage page should eventually show totals from the available environment and clearly mark the offline environment as unavailable/incomplete. A disconnected device should reach a terminal error state or be excluded after a bounded timeout.
Actual behavior
The page remains on its loading skeleton indefinitely with “1 device still scanning.” The online environment completes successfully, while the offline environment is reconnecting and reports a 10-second remote endpoint timeout under Settings → Connections.
The remote usage request appears to remain pending instead of becoming a failure. In the current client flow,
useUsage()treats an environment with no summary and no error as still reporting, andUsagePagedeliberately holds all content whileisPending || isPartial. Because the unreachable environment never becomes terminal, the page never displays even the completed device's totals.Impact
Major degradation or frequent failure
Version or commit
0.0.34-nightly.20260810.1061
Environment
macOS desktop app; two remembered Mac environments connected using Tailscale HTTPS; one remote Mac asleep/unreachable.
Logs or stack traces
The Connections screen continues showing “Failed to connect. Reconnecting...” / “Connecting...” while Usage remains on “1 device still scanning.”
Workaround
Wake the remote Mac so it reconnects, or temporarily remove the offline environment under Settings → Connections → Remote environments.