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.
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?)
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 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>]`
2025-10-1410:49:35.573 [warning] ssh: failed to start SSH agent, clones may not work as expected: ‘Error: Command exited with non-zero code (1): PID 10436: [powershell.exe -Command \n’ +