Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCodium/WindSurf/Cursor support #408

Open
4 tasks
matifali opened this issue Dec 12, 2024 · 13 comments
Open
4 tasks

VSCodium/WindSurf/Cursor support #408

matifali opened this issue Dec 12, 2024 · 13 comments

Comments

@matifali
Copy link
Member

matifali commented Dec 12, 2024

Coder’s current VS Code extension relies on ms-vscode-remote.remote-ssh, which is only available via the Microsoft Marketplace. This limits compatibility with non-Microsoft VS Code forks such as VSCodium, Cursor IDE, and Windsurf, which cannot access the Microsoft Marketplace. Users in air-gapped or privacy-focused environments need a version of the Coder extension that works without this dependency.

Desired Solution

  • Create a Coder extension variant that is compatible with VSCodium, Cursor IDE, Windsurf, and other VS Code forks by using an open-source SSH extension such as jeanp413.open-remote-ssh.
  • Publish this extension on Open VSX for easy access.
  • Create terraform modules for these editors, similar to the existing VS Code Desktop module.

Implementation Requirements

Related Issues:

@matifali
Copy link
Member Author

matifali commented Dec 12, 2024

@code-asher We have now requests for VSCodium, Windsurf and a buggy behavior on Cursor too.
We may need to ship a new separate binary without relying on the MS remote SSh extension as it only works on the MS version of VSCode.

cc: @bpmct

@matifali matifali transferred this issue from coder/coder Dec 12, 2024
@coder-labeler coder-labeler bot added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Dec 12, 2024
@matifali matifali changed the title Feature Request: VSCodium support VSCodium/WindSurf/Cusror support Feb 20, 2025
@matifali
Copy link
Member Author

@f0ssel @bcpeinhardt 'Let''s pull this into the current sprint.

@matifali matifali added customer-requested and removed documentation Improvements or additions to documentation help wanted Extra attention is needed labels Feb 20, 2025
@matifali

This comment has been minimized.

@matifali
Copy link
Member Author

Discussed in coder/coder#15846

Originally posted by asgeirn December 12, 2024
We're investigating using Coder in an isolated environment with no Internet connectivity, and according to the documentation for offline deployment, VSCode requires outbound port 443 access for the remote SSH extension to work.

I tried installing the Coder VSIX in VSCodium, but it fails because it depends on the ms-vscode-remote.remote-ssh extension. According to VSCodium/vscodium#693 the extension 'jeanp413.open-remote-ssh' does this.

Would it be possible to provide a variant of the Codium extension on Open VSX for this, and a module for creating "Open in VSCodium" links in workspaces?

@matifali matifali marked this as a duplicate of #269 Feb 25, 2025
@matifali
Copy link
Member Author

WindSurf does not use both Microsoft SSH and Open Remote SSH extensions and has its own built-in implementation.
Ref: https://docs.codeium.com/windsurf/advanced#ssh-support

@f0ssel
Copy link
Contributor

f0ssel commented Feb 25, 2025

I've updated the Implementation Requirements in the OP to include decomposed issues for the tasks needed to accomplish this effort:

Implementation Requirements

@bcpeinhardt
Copy link
Collaborator

The PR mentioned above works around the existing issue by moving MS Remote SSH to be part of an extension pack rather than a hard dependency, and searching for open source alternatives which may be installed, enabling support for VS Code, Cursor, and Windsurf at the same time.
Per standup conversation on doing the simple implementation and coming back to swapping out the SSH dependencies entirely when we have more capacity, moving this ticket to done.

@matifali
Copy link
Member Author

@bcpeinhardt, we should publish to the OpenVSX registry to be used by WindSurf and other OSS alternatives.
Also, the PR solves coder/internal#430 only and we still need #269

@bcpeinhardt
Copy link
Collaborator

bcpeinhardt commented Mar 11, 2025

@matifali On the topic of publishing, uploading to the Microsoft VSCode Marketplace is manual at the moment. I've simply added to the contributing docs that the built .vsix needs to be uploaded to OpenVSX Marketplace as well: https://github.com/coder/vscode-coder/pull/451/files#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055R138

Since the MS Remote Extension has been moved from a dependency to instead be part of an extension pack, we should be able to upload there, but I did move this too early. I'll move back to in progress until the new build is successfully published to both repositories.

@bcpeinhardt bcpeinhardt reopened this Mar 11, 2025
@matifali matifali marked this as not a duplicate of #269 Mar 12, 2025
@matifali
Copy link
Member Author

version 1.5.0 works as expected in WindSurf and Cursor
for VSCodium, I get,

command 'coder.login' not found

As per VSCodium/vscodium#1777, I installed Open Remote SSH extension.

@EdwardAngert EdwardAngert changed the title VSCodium/WindSurf/Cusror support VSCodium/WindSurf/Cursor support Mar 24, 2025
@asgeirn
Copy link

asgeirn commented Apr 2, 2025

In VSCodium, extension from Open VSX installs without issue, but I get this error if I select Coder Remote in the Activity Bar:

2025-04-02 14:02:23.706 [info] ExtensionService#_doActivateExtension coder.coder-remote, startup: false, activationEvent: 'onView:myWorkspaces'
2025-04-02 14:02:23.799 [error] Activating extension coder.coder-remote failed due to an error:
2025-04-02 14:02:23.799 [error] Error: Remote SSH extension not found

I have jeanp413.open-remote-ssh installed.

@matifali
Copy link
Member Author

matifali commented Apr 2, 2025

Thanks, @asgeirn We have yet to solve for VSCodium by adding support for jeanp413.open-remote-ssh

We are open to contributions, too.
This is on our roadmap, but I don't have a clear ETA on when we can complete this.

@asgeirn
Copy link

asgeirn commented Apr 3, 2025

Thanks for your response! I did a small test on my setup, and it would appear #467 is sufficient to get it to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants