Skip to content

[Bug] [UI]: Remote threads missing, new option almost invisible in dark mode, defaults to off when servers were configured previously #14979

Description

@michft

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

Steps to reproduce

Close if appropriate. Debugging with GPT did not see new options in setup.

  1. Open Settings → Connections.
  2. Scroll to Environments.
  3. Inspect saved remote environments with their switches Off. (Were "on" 24h ago)

Expected behavior

Environment switches remain clearly visible and recognizable as controls in both states. Off state should be distinguishable from an unavailable control.

Actual behavior

Off switches blend into dark background. Environment names, URLs and “Off” labels also appear faint. Switches look unavailable rather than visibly interactive; hover tooltip says “Switched off.”

Discovered this while investigating missing remote threads from M’s Mac mini and Raspberry Pi 5 (compromised3). Both saved environments show Off.

Impact

Cosmetic issue

Version or commit

t3@0.0.46-nightly.20261003.2610

Environment

Client: macOS, Apple Silicon, T3 Code Nightly. Remote hosts: Mac mini and Raspberry Pi 5 running 64-bit ARM Linux. Saved connections: HTTP over a private network and HTTPS through Tailscale Serve. Direct browser access: Zen.

Logs or stack traces

Settings → Connections displays:

Mac mini: Client not supported
Raspberry Pi: Client not supported

Both connection switches are disabled.
No relevant stack trace captured yet.

Screenshots, recordings, or supporting files

Screenshot 2026-10-03 at 12.28.40.png
Screenshot 2026-10-03 at 12.35.32.png
Screenshot 2026-10-03 at 12.20.02.png
Screenshot 2026-10-03 at 12.37.13.png

Workaround

Turn them on (PEBKAC) buttons very hard to see, changed configured default with new option.

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Oct 3, 2026
  2. juliusmarminge commented on Oct 3, 2026

    @juliusmarminge
    Member

    Note

    Grok responding on behalf of Julius.

    Triage

    Thanks for the detailed report and the screenshots, @michft.

    Missing remote threads: your screenshots point to the environment switches, not a sync bug. On 0.0.46-nightly.20261003.2610, both saved environments (M's Mac mini and compromised3) are Off, and the tooltip says Switched off. A saved environment's threads only load while its switch is on, so turning them back on is the right fix. Saved environments don't default to off. They stay on unless something adds them to the switched-off list.

    The "Client not supported" note: that message is a different state. It means this client can't speak the server's protocol, so the switch is disabled, and that incompatibility is saved as switched off. The reason isn't stored, so on a later launch the row only shows Off with the Switched off tooltip, which matches your last screenshot. This nightly uses the new orchestrator protocol (merged in #2829). If the Mac mini or the Pi are still on an older build, update them to this same nightly. Otherwise, turning a row back on will connect, fail the compatibility check, and flip back to "Client not supported".

    Dark-mode contrast: this part is a real bug, and it's what this issue will track. A switched-off row is drawn at 60% opacity. The unchecked switch uses the dark-theme input track (white at 8%), and its thumb is the same color as the background. On the dark Connections page that makes the control easy to miss and easy to mistake for a disabled one, which matches the faint names, URLs, and "Off" labels in your screenshots. Dimming the row is intentional, but the switch itself shouldn't disappear.

  3. added
    via-triageFiled through npx t3 triage
    and removed
    needs-triageIssue needs maintainer review and initial categorization.
    on Oct 3, 2026
  4. michft commented on Oct 3, 2026

    @michft
    Author

    All were updated to same build doing issue checking using ssh for linux and screensharing for mini. Did not make controls more visible. Threads 'came back' when the remote machines were switched to on in local laptop.

  5. joao-coli commented on Oct 3, 2026

    @joao-coli

    +1 to the brightness issue on the switch. In dark mode and on my OLED display it was barely noticeable, if at all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.via-triageFiled through npx t3 triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions