[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
Introduces subprocess execution and external URL opening with tightened allowlists; server config stream shape and WS wiring change, but scope is feature-flagged via settings defaults.

Overview
Adds VS Code remote tunnel support end-to-end: the server can detect an active code tunnel, expose it on the server config WebSocket stream, and the chat Open control can launch the workspace in vscode.dev or the desktop app.

Server & contracts: New vscodeTunnel / vscodeTunnelStatus on ServerConfig, settings enableVSCodeRemoteTunnels and openVSCodeRemoteTunnelsInDesktop, and a vscodeTunnelUpdated stream event. A VSCodeTunnelMonitor runs code tunnel status (with robust JSON extraction), caches results, refreshes on settings changes and on a 1-minute tick, and feeds a centralized PubSub fan-in for subscribeServerConfig (replacing per-handler merges for keybindings/providers/settings).

Desktop & web: Electron openExternal now allows only vscode://vscode-remote/tunnel+... URLs (not arbitrary vscode: links). OpenInPicker gains a tunnel menu entry and primary action when no cross-environment editor picker is shown; links use shell.openExternal. Connections settings show tunnel status and the two toggles.

Tests: Coverage for URL allowlisting, tunnel JSON parsing, monitor caching, client config projection, and server WS subscription behavior.

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

Note

Add VS Code remote tunnel editor support to the server config stream and UI

• Adds a VSCodeTunnelMonitor service (vscodeTunnel.ts) that periodically runs code tunnel status, parses the output, and publishes updates via a PubSub stream
• Extends the server config WebSocket stream with a new vscodeTunnelUpdated event type and includes vscodeTunnel/vscodeTunnelStatus fields in the config snapshot
• Adds an OpenInPicker option in the chat header to open the current path via a VS Code remote tunnel (web vscode.dev URL or desktop vscode:// URL based on settings)
• Adds two settings in ConnectionsSettings: toggle tunnel monitoring (enableVSCodeRemoteTunnels) and choose desktop vs. browser target (openVSCodeRemoteTunnelsInDesktop)
• Extends parseSafeExternalUrl in ElectronShell.ts to allow vscode://vscode-remote/tunnel+* URLs through the external link safety check

^{Macroscope summarized 941fe4c.}

[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: 1c038ec9-8f17-425e-a353-1e2f9ceaf90c

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

2 blocking correctness issues found. This PR introduces a new VS Code tunnel feature with new settings, UI components, and background monitoring across multiple packages. The scope of new capability warrants human review, and there are two unresolved review comments identifying potential bugs in the JSON parsing and race condition handling.

^{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}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3eb9989. Configure here.}

[juliusmarminge]

this UX doesn't make sense does it? why show both normal vscode as well as vscode remote? normal vscode and finder wont work for remote envs? shouldn't it be mutually exclusive??

[huxcrux]

this UX doesn't make sense does it? why show both normal vscode as well as vscode remote? normal vscode and finder wont work for remote envs? shouldn't it be mutually exclusive??

I definitely agree. I'll look into this later today.

[juliusmarminge]

would be good to have the architecture support adding zed remote and jetbrains as well in a follow up so make sure it's not too tied to only vscode

[huxcrux]

Closeing this PR and will open another one with SSH support once I can get my local dev environment to behave with remote sessions