Cursor Remote SSH SOCKS5 proxy only binds IPv6 localhost — cannot connect via IPv4 localhost

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When connecting to a remote server via Cursor Remote SSH, the connection fails with
ECONNREFUSED 127.0.0.1: errors if the server is accessible via IPv6.

It looks like Cursor’s internal SOCKS5 proxy (spawned as part of the SSH tunnel) only binds to IPv6 localhost (::1), not IPv4 localhost (127.0.0.1).

VSCode Remote SSH works fine with the same host — the issue only occurs in Cursor.

Steps to Reproduce

Have a remote Linux server accessible via IPv6 (and optionally IPv4).

In Cursor, set up a Remote SSH connection to that host (e.g. ssh user@host where host resolves to an IPv6 address).

Observe the connection logs:

Cursor spins up a SOCKS5 proxy (with -D ).

The proxy listens only on IPv6 localhost (::1).

Cursor fails to fetch the remote environment with error:

Could not fetch remote environment
Failed to connect to the remote extension host server
(Error: WebSocket close with status code 1006)

Logs show:

error while creating socks forwarding connect ECONNREFUSED 127.0.0.1:

Expected Behavior

Cursor should make its internal SOCKS5 proxy listen on both IPv4 (127.0.0.1) and IPv6 (::1) localhost so IPv4 connections don’t fail.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.43
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.12.48-1-MANJARO

Does this stop you from using Cursor

No - Cursor works, but with this issue