Windows desktop offers "Add route" for its own WSL backend in the Environments list #27463

What happened

In Settings → Connections → Environments on the Windows desktop app, a row named "computer" appears with the status "T3 Connect · Saved without T3 Connect · Relay online" and an Add route button. "computer" is the Windows machine's name, so the app seems to be offering to add the machine you are already using.

Screenshot:

Diagnosis

The row is the desktop app's own WSL backend, not the Windows host. WSL takes its hostname from Windows, so both environments are labeled computer. The Windows server reports platform.os: windows on port 3773. The WSL Ubuntu backend reports platform.os: linux on port 3774, and the row shows the Tux icon. The WSL backend is linked to T3 Connect, so relay discovery returns it.

ConnectionsSettings.tsx hides desktop-local backends from the saved rows: listedEnvironments filters out isDesktopLocalConnectionTarget. It still passes the unfiltered savedEnvironments to CloudRemoteEnvironmentRows. In CloudEnvironmentConnectList.tsx, isVisibleEnvironment only excludes primaryEnvironmentId. The WSL backend has a different environment ID, and its desktop-local entry has no relay route. So it lands in savedWithoutRelay, which renders "Saved without T3 Connect" and Add route.

Possible fix: leave desktop-local environments out of the T3 Connect discovery rows, the same way the saved list does. Sidebar.tsx, DraftHeroHeadline.tsx and ConnectOnboardingDialog.tsx use the same component and may show the same row (not checked).

The code is unchanged between the v0.1.5 tag and main as of 2026-10-30.

Steps to reproduce

1. On Windows, run T3 Code Desktop with the WSL backend enabled next to the Windows backend.
2. Link the WSL backend to T3 Connect, so it shows as online in T3 Connect.
3. Open Settings → Connections → Environments.
4. A row with the Windows hostname and a Tux icon appears, showing "T3 Connect · Saved without T3 Connect · Relay online" and an Add route button. The WSL backend has no row in the saved list above it.

Version

0.1.5 (desktop app, Windows server and WSL backend)

Environment

Windows 11 Pro 10.0.26200 x64, Node v24.22.1, WSL2 Ubuntu

Evidence

# Windows server: GET http://127.0.0.1:3773/.well-known/t3/environment
{"environmentId":"357f9df0-…","label":"computer","platform":{"os":"windows","arch":"x64"},"serverVersion":"0.1.5",…}

# WSL backend (from inside WSL): GET http://127.0.0.1:3774/.well-known/t3/environment
{"environmentId":"86b2e888-…","label":"computer","platform":{"os":"linux","arch":"x64","machine":"linux"},"serverVersion":"0.1.5",…}

# Desktop backend log for instanceId wsl:Ubuntu: the WSL backend publishes to T3 Connect
INFO: agent activity publish completed { environmentId: '86b2e888-…', … }

# Settings row as shown
computer   T3 Connect · Saved without T3 Connect · Relay online   [Add route]

Related issues

#22629 (open PR) labels WSL environments with their Windows host; that would make this row less confusing but would not stop it being listed. No existing issue reports this row.

Fix applied or workaround

None. The row only looks wrong; the WSL backend works through its local connection.

Filed by

Claude Code (claude-opus-5-5) via t3 triage