feat(web): open remote worktrees in Zed

[husseinraoouf]

Closes #7899

Problem

The generalized remote editor links from #6572 only understand VS Code's vscode-remote URL shape. Zed therefore remains local-only even though #4361 was closed, while its older dedicated implementation in #4362 predates the generalized flow. Zed Preview was not tracked.

Fix

• describe each remote-capable editor's URL shape in the shared editor registry
• build Zed's official zed://ssh/<host>/<path> hotlinks while preserving the existing host/path encoding
• include Zed in the desktop-side local editor probe
• allow only structurally valid Zed SSH hotlinks through Electron's external URL boundary
• document that stable Zed and Zed Preview share the zed:// handler, so users select Preview by registering the scheme from Preview

This follows Zed's documented remote-development URL format and its shared release-channel URL scheme. It avoids reviving the separate Zed-only IPC path from #4362.

Verification

• vp test run apps/web/src/remoteOpen.test.ts apps/desktop/src/electron/ElectronShell.test.ts � 20 tests passed
• vp run --filter @t3tools/contracts --filter @t3tools/desktop --filter @t3tools/web typecheck
• targeted vp lint for changed TypeScript files
• targeted vp fmt --check for all changed files
• git diff --check

UI changes

No layout or styling changes. Zed now appears in the existing remote Open picker when its local CLI is detected.

Implemented by Codex (gpt-5.6-sol) through the T3 Code Codex harness.

---

Note

Medium Risk
Changes Electron’s external URL allowlist and deep-link generation; mistakes could open unsafe custom schemes or break remote open for VS Code-family editors.

Overview
Adds Zed to the shared remote “Open in editor” flow using Zed’s zed://ssh/<host>/<path> hotlinks, alongside the existing VS Code-family vscode-remote shape.

The editor registry now declares a RemoteEditorUrlStyle per remote-capable editor; buildRemoteOpenUrl branches on that style (Zed vs VS Code forks). REMOTE_CAPABLE_EDITOR_IDS only includes editors with both scheme and style, so Zed shows up in the remote Open picker when its CLI is detected.

On desktop, ElectronShell validates editor deep links by style—allowing well-formed Zed SSH URLs while still blocking unrelated zed:// routes and URLs with userinfo. Tests and user docs cover Zed/Zed Preview scheme registration.

^{Reviewed by Cursor Bugbot for commit 4113f02. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add Zed as a remote-capable editor with zed://ssh/ deep links

• Introduces RemoteEditorUrlStyle union type and optional remoteUrlStyle on EditorDefinition in editor.ts, so each remote editor declares its deep-link shape
• Adds remoteScheme: 'zed' and remoteUrlStyle: 'zed-ssh' to the Zed editor entry; VS Code-family editors now explicitly declare remoteUrlStyle: 'vscode-remote'"- buildRemoteOpenUrl builds zed://ssh/<host>/<path> for Zed and continues to build <scheme>://vscode-remote/ssh-remote+<host><path> for VS Code-family; returns undefined when either scheme or style is missing
• isRemoteEditorUrl in ElectronShell.ts replaces the flat protocol allowlist with a protocol→style Map and validates URL shape per style: Zed links require host ssh plus non-empty host and path segments; VS Code links require host vscode-remote and a /ssh-remote+ prefix
• Behavioral Change: REMOTE_CAPABLE_EDITOR_IDS now requires both remoteScheme and remoteUrlStyle; editors missing either are excluded from remote-capable listings. Malformed Zed URLs (non-remote or missing path) are now rejected

^{Macroscope summarized 4113f02.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1c8d7816-d8b4-4997-8cfc-1093235c01c7

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Skipped

Macroscope did not run approvability analysis for this PR. Macroscope could not determine whether this PR modifies its approvability configuration, so the PR was not approved automatically. A PR that may change the rules that govern approval is never approved automatically.

[husseinraoouf]

@juliusmarminge i know you have alot on your plate, but i would appreciate if you could get this into nightly it would be a huge un-blocker for me