Add VS Code tunnel editor support

[huxcrux]

What Changed

Support for VSCode tunnels was added. VSCode tunnels allows a user to access a remote VSCode instance over the internet. This makes it possible to use T3Code on a remote machine and open a VSCode window like the code was local.

Why

To make remote workflows easier for VSCode users

UI Changes

Editor dropdown:

Settings:

Checklist

• This PR is small and focused
• I explained what changed and why
• I included before/after screenshots for any UI changes
• I included a video for animation/interaction changes

---

Note

Medium Risk
Runs external code CLI on the server and widens desktop external URL rules for a specific vscode-remote tunnel pattern; otherwise mostly additive UI and config streaming.

Overview
Adds VS Code remote tunnel support so remote environments can expose a connected tunnel and open the current workspace in VS Code (browser or desktop).

The server runs code tunnel status (when enabled), parses noisy CLI output into tunnel + status fields, and includes them on server config snapshots and vscodeTunnelUpdated stream events (on setting changes and ~1 minute refresh). Contracts and client projection gain vscodeTunnel, vscodeTunnelStatus, and settings enableVSCodeRemoteTunnels / openVSCodeRemoteTunnelsInDesktop.

Open in can show a tunnel option (including when local editors are hidden), building vscode.dev or vscode://vscode-remote/tunnel+... URLs via the desktop shell API. Connections settings add toggles for enabling checks and desktop vs web open. Electron openExternal now allows only tunnel-shaped vscode:// URLs, not arbitrary vscode:// links.

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

Note

Add VS Code remote tunnel editor support to the open-in picker and settings

• Adds a new resolveVSCodeTunnel effect in vscodeTunnel.ts that runs code tunnel status, parses its JSON output, and returns tunnel presence, machine name, and connection state.
• Extends the WebSocket subscribeServerConfig stream to emit vscodeTunnelUpdated events when the enable setting changes or on a 1-minute refresh interval.
• Adds VS Code tunnel fields to ServerConfig snapshots and a new vscodeTunnelUpdated stream event to the RPC contracts in server.ts.
• Adds two new server settings (enableVSCodeRemoteTunnels, openVSCodeRemoteTunnelsInDesktop) with toggles in the Connections settings UI.
• Extends OpenInPicker to show a 'VS Code Tunnel' option that opens the current directory via a vscode://vscode-remote/tunnel+… or vscode.dev URL, with the primary button and keyboard shortcut tracking the last chosen option.
• Updates parseSafeExternalUrl in ElectronShell.ts to allow vscode://vscode-remote/tunnel+… URLs for openExternal.

^{Macroscope summarized 146c285.}

[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

Run ID: db476ac2-c913-4f38-b545-178708563157

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces a new VS Code remote tunnel feature with external process invocation, new streaming events, new settings, and UI changes across multiple packages. The scope and new integrations warrant human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[macroscopeapp]

Effect service convention: consume the local ProcessRunner service module through its namespace rather than importing the service tag directly.

^{Posted via Macroscope — Effect Service Conventions}