Skip to content

[Bug]: Open in offers only VS Code over SSH when the saved environment is the same Mac #18473

Closed

Description

@grahamfarrar

Before submitting

Area

apps/desktop, apps/web

Setup

T3 Code 0.0.45 on macOS. The server runs as a background service on the same Mac (127.0.0.1:3773). The desktop app
has Local environment turned off and connects to that service as a saved environment, so the app and the server
share one database instead of the app starting a second server.

Steps to reproduce

  1. Settings → turn off Local environment; add a saved environment at http://127.0.0.1:3773 on the same Mac.
  2. Open any thread and click the chevron next to Open in the header.

Expected behavior

Since the environment is the machine the app is running on, Open in offers the same targets as a local environment:
Finder and any installed editors, opening the path directly.

Actual behavior

The menu has one entry: "VS Code - Opens over SSH. Needs your key on ". Finder is not offered, and with no
VS Code installed there is no way to open the folder from T3. The same applies to file and folder chips in chat:
right-click offers only "Copy relative path" and "Copy full path", with no "Reveal in file manager" (the workaround
#15215 mentions for folder chips).

Suggestion

Treat a saved environment whose host is loopback (or whose server reports the same machine ID as the desktop app)
as local for Open in.

Activity

  1. juliusmarminge commented on Oct 12, 2026

    @juliusmarminge
    Member

    Note

    Grok responding on behalf of Julius.

    This setup isn't supported, so I'm closing this with a workaround. On main, resolveRemoteOpenState (apps/web/src/remoteOpen.ts, from #6572) treats only the desktop app's own Local backend as local. Every saved environment goes through SSH links, even one at 127.0.0.1, and the server reports no machine ID that would let the app tell it's the same Mac.

    Workaround: turn Local environment back on. Open in, Finder and "Reveal in file manager" then work as usual.

    Treating loopback or same-machine saved environments as local would be a feature request. It's closely related to #7530, which hits the same gap with a browser on a LAN IP. If you want it, please open it in Ideas.

  2. fu5ha commented on Oct 17, 2026

    @fu5ha

    The workaround no longer works as the app will not start up due to #16102 (related: #20250)

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

    questionFurther information is requestedvia-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