Cursor VS CODE / Microsoft Remote Tunneling issues and the definitive support thread

Bug Reports
1

Based on figuring this out prior using the Github issues like this one:

It seems like Cursor and Remote Tunneling needs a support thread or page and a how to…

The approach that worked a few months ago is not working now (or today?)

The Cursor approach was:

  1. Download the Cursor CLI on your remote machine:

curl -Lk ‘https://api2.cursor.sh/updates/download-latest?os=cli-alpine-x64’ --output cursor_cli.tar.gz

  1. Extract the CLI:

tar -xf cursor_cli.tar.gz

  1. Create a secure tunnel:

./cursor tunnel

Which mirrored the VS Code documented approach on the MS website…

This worked for me - per Tom’s helpful posts over on that Issue post.

So, I don’t know what versions of which CLI is need or why, but more specifically where do we find what is available?

Today, I could not open up the tunnel for Cursor off the same server. Rebooted, grabbed the cli, tried it again. But, the VS Code CLI worked like a charm…

So what gives currently?

thanks

David

2

so many threads asking for a tunnel guide and silence from the cursor team. I’m cancelling my membership until they answer.