Describe the Bug
Subject: Compatibility Issue with Anysphere Remote-SSH Plugin When Connecting via Jumpserver
Description:
The Microsoft Remote-SSH extension functions correctly when connecting to our remote development server through a jumpserver (bastion host) using the following command format:
ssh jumpserverUsername@systemUsername@AssetIP@jumpserverHostIP -p2222
Example (working in VS Code):
ssh sunzhenping@[email protected]@192.168.18.6 -p2222
This configuration follows Jumpserver’s nested authentication protocol (reference: https://kb.fit2cloud.com/?p=48).
However, Anysphere’s Remote-SSH plugin fails to establish connections using the same jumpserver method. Notably, direct SSH connections (e.g., ssh [email protected]) work without issues, confirming that:
- The target server is accessible.
- The jumpserver workflow is the root cause.
Impact:
This blocks development workflows as our company mandates jumpserver-based access for security compliance. The issue persists across repeated attempts.
Request:
Investigate Anysphere Remote-SSH’s compatibility with Jumpserver’s multi-hop SSH syntax and implement support for this enterprise authentication model.
Steps to Reproduce
ssh jumpserverUsername@systemUsername@AssetIP@jumpserverHostIP -p2222
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.3.9
VSCode Version: 1.99.3
Commit: 54c27320fab08c9f5dd5873f07fca101f7a3e070
Date: 2025-08-01T20:07:18.002Z
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
Additional Information
Name: Remote - SSH
Id: anysphere.remote-ssh
Description: Open any folder on a remote machine using SSH and take advantage of Cursor’s full feature set.
Version: 1.0.23
Publisher: Anysphere
Does this stop you from using Cursor
Yes - Cursor is unusable
