Skip to content

Open remote worktrees in local Zed or Zed Preview #7899

Description

@husseinraoouf

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

The generalized remote editor flow merged in #6572 only gives remoteScheme support to VS Code-family editors. Zed remains a local-only editor, so using Open on a remote worktree cannot hand the local Zed app the remote SSH workspace.

#4361 previously tracked stable Zed and was closed as completed when #6572 merged, but #6572 explicitly excluded Zed because its remote URL shape differs. The older implementation in #4362 is still open and predates the generalized remote-link architecture. Neither tracker covers the remaining gap accurately, and neither covers Zed Preview.

Proposed solution

Extend the generalized remote editor URL model to support Zed's official SSH hotlink shape:

zed://ssh/<host>/<absolute-path>

Make the existing Zed editor remote-capable so desktop probing offers it alongside VS Code-family editors. This should work with both stable Zed and Zed Preview: Zed uses the same zed:// scheme for every release channel, so the channel that has registered itself as the OS handler opens the worktree. Document how Preview users can make Preview the handler.

Preserve the existing host/path percent-encoding and Electron external-URL safety checks, with focused tests for URL construction and allowlisting.

Why this matters

Remote T3 Code users should be able to open the exact worktree in their local Zed installation without manually constructing an SSH URL. Zed Preview users need the same workflow and should not be left with an apparently separate, unsupported variant.

Smallest useful scope

  • Stable Zed and Zed Preview through their shared official zed://ssh/... hotlink
  • Existing remote-link modes (desktop-managed SSH alias and server-advertised SSH host)
  • Folder-level open only
  • Focused contract/web/desktop tests and remote-access documentation

Alternatives considered

Risks or tradeoffs

Stable and Preview cannot be selected independently through a URL because they share the same OS scheme. The most recently registered Zed channel handles the link, which should be explained in the docs.

Examples or references

Contribution

  • I would be open to helping implement this.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions