Enhancing SSH Connection Compatibility with Cursor #225
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previous MR #221
Overview
I have been a dedicated user of both Coder and Cursor. However, I've encountered persistent issues when attempting to connect to the Coder workspace via Cursor (Cursor). These issues range from receiving 404 errors to SSH connection failures, preventing any access to the workspace. The root cause of these problems lies in the necessity to use Cursor's built-in Open Remote - SSH extension,
anysphere.open-remote-ssh
, for successful SSH connections.Changes Made
I've confirmed that users utilizing Cursor can simply specify
anysphere.open-remote-ssh
explicitly within the Coder plugin without any issues coexisting withms-vscode-remote.remote-ssh
. Therefore, I've made a straightforward update to check for the existence ofanysphere.open-remote-ssh
and use it preferentially if available. This eliminates the need to remove any dependencies.With this MR, I'm hopeful for a seamless integration between Cursor and Coder, which I personally believe is the best combination.