AWS Toolkit <> Remote - SSH

Bug Reports
1

Describe the Bug

It seems Microsoft’s “Remote - SSH” no longer shows up in Extensions, in favor of Anysphere’s “Remote - SSH”. However, this seems to cause problems with other extensions that look for the Microsoft version, such as the AWS Toolkit (see screenshot).

I tried clicking on “Connect to SageMaker Space” in the AWS Toolkit, but got the error:

Connecting to Dev Environment requires the Remote SSH extension (‘ms-vscode-remote.remote-ssh’ of version >=0.74.0) to be installed and enabled.

Even though the Remote - SSH extension by Anysphere is already installed.

Steps to Reproduce

Try to use AWS Toolkit to connect to a remote SageMaker Space (e.g. JupyterLab or Code Editor). Detailed steps: Supercharge your AI workflows by connecting to SageMaker Studio from Visual Studio Code | Artificial Intelligence

Screenshots / Screen Recordings

screenshot.jpg
screenshot.jpg1851×1288 242 KB

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.4.2
VSCode Version: 1.99.3
Commit: d01860bc5f5a36b62f8a77cd42578126270db340
Date: 2025-08-07T17:16:23.005Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
3

Bump — any way to get compatibility with Microsoft’s Remote - SSH?

5

Also facing this issue, on Ubuntu 24.04 LFS.

This is quite a severe shortfall as I do the bulk of my dev work on EC2 machines, which I’m no longer able to connect to with Cursor.

7

Also facing this issue.

9

Hi, taking a look at this issue. What version of the AWS Toolkit are you using?

10

3.73.0… the latest version

12

Thanks for confirming. We tried testing this version as well, but ran into Build missing webpack files? · Issue #7915 · aws/aws-toolkit-vscode when attempting to replicate the correct behavior in VSCode. Could you confirm that you are able to connect to the instance from within VSCode (if you have that installed?)

13

Yes I can confirm it works from VSCode(I’ve been using AWS Toolkit from within VSCode on a daily basis since the issue arose).

Happy to set up a call+screen share if that would help shed some light.

Thanks
Vinay

15

Hi @Vinay_Maniam, could you try the nightly build of Cursor? We pushed some fixes yesterday that should help with this particular error, but we weren’t able to fully validate that this was the only issue impeding the connection.

The nightly build can be downloaded at Nightly Downloads | Cursor - The AI Code Editor

16

Hi Ravi

When will this update be rolled out to main? If it’ll be in the next couple days then I’d rather wait and ingest the update normally.

Thanks
Vinay

18

It is available under pre-release and should be rolling out more broadly this week.

19

The original error is solved, but I get another error:

`sm:OpenRemoteConnect: Unable to connect to target space with arn: error: Error: Command exited with non-zero code (1): PID 66019: [/Applications/Cursor.app/Contents/Resources/app/bin/code --folder-uri vscode-remote://ssh-remote+sagemaker-user@<path_to_folder>]`

Why is it trying to use `vscode-remote`?

21

Hi @ravirahman ,

I’m on the latest version of Cursor and I still run into the same issue. Have there been any developments on this?

Thanks

Vinay

23

Hi @Vinay_Maniam, we are working with AWS to resolve this issue.

1 Like