Feature Request: Open Current Workspace Directly in VS Code (Local or Remote SSH) #63

Activity

1. malys commented on Aug 23, 2026

   

   malys

   on Aug 23, 2026

   Author

   More actions

   Thanks with your high reactivity, CCS is improved quickly. Thanks.
2. Lexus2016

   closed this as completedin #65on Aug 24, 2026
3. Lexus2016

   added a commit that references this issue on Aug 24, 2026

   feat: open the active workspace in VS Code, local or over SSH (#63) (#65

   ...

   4ae8659
4. Lexus2016 commented on Aug 24, 2026

   

   Lexus2016

   on Aug 24, 2026

   Owner

   More actions

   Shipped in #65 (v7.8.0). Thanks for the detailed write-up — the local/remote split in it is exactly the shape the implementation took.

   What landed

   • Open in editor from the project row and from the file viewer.
   • Local → code <workspace>.
   • Remote SSH → VS Code Remote-SSH straight at the recorded path, no manual reconnect. A non-standard port is carried into the authority.
   • Editor choice in Settings → UI: VS Code, Insiders, VSCodium, Cursor, Windsurf.

   On detection and the fallback

   The studio is not always running on the machine the browser is on, so there are two launch paths and the server picks between them:

   • it finds a code binary on $PATH → it opens the window itself and can report a failure honestly;
   • it finds none (Docker, headless host, Windows) → it hands your browser a vscode:// deep link, which lands on the machine with the screen.

   One rule, no platform detection, correct in every deployment. The honest caveat: nothing about the deep-link outcome is observable — no browser reports whether a protocol handler exists or ran — so on that path the UI states the condition ("if nothing opened, …") rather than claiming an error it cannot see. The same is true of the Remote-SSH extension: its presence isn't detectable from here, so it's named in that hint instead of being probed.

   What I deliberately left out

   • Remote per-file open. The remote folder link works; VS Code's own URL handler opens a remote file URI as a folder (vscode-remote-release#4333). A button that opens the wrong thing is worse than no button, so it's hidden for remote files — the project row still opens the remote workspace. Per-file open works locally.
   • "Reveal current file" / "Open terminal in VS Code." Neither has a URI or CLI primitive that behaves correctly across the local/remote split. Happy to revisit if you know one.

   One thing worth flagging: a remote project recorded with a ~/project workdir is refused by name rather than opened. A URI has no shell, so Remote-SSH would look for a directory literally called ~. If you hit that, re-create the project with the full path on the host.