mac mini cursor tunnel

I ran into some issues:

1. Connecting to the tunnel using GitHub auth.
2. Connecting to the tunnel with Cursor.
3. Keeping the tunnel live.

Recently I started playing around with Cursor, as I thought I’d give it a shot. Since I’m going to have to use VSCode for some things, I might as well try one of the forks that just received a NINE BILLION DOLLAR VALUATION (WHAT IS HAPPENING?).

connecting to the tunnel using github auth

cursor tunnel

Then click on any link produced by the output and sign in with your GitHub account / select your preferred method of authentication.

connecting to the tunnel with cursor and keeping it live

I made the mistake of thinking that the VSCode fork (Cursor) was compatible with VSCode tunnels… and I was wrong. It’s a known issue, and the workaround is to just use Cursor to run the tunnel, not a default deployment of VSCode.

Since I’m using it on a Mac Mini Homelab, I run it as a service:

cursor tunnel service install

My backup in the case that doesn’t work (for whatever reason) is:

cursor tunnel --no-sleep

Ensure you’re running it with cursor instead of code if you are indeed using Cursor on your dev machine / laptop.

That’s it! Hopefully it stays live. Let me know if you run into any issues or weird edge cases.

Hi, I'm alp1n3

This is a collection of my cybersecurity notes & projects.

I graduated from Dakota State University with a MS in Cyber Defense & BS in Cyber Operations. Since then I've worked as a Malware Analyst with the U.S. Army Cyber Command, and am now a Web Application Security Consultant.

I'm a big fan of open security standards for applications and workflow automation when it comes to security testing. The easier it is to identify and replicate, the more secure everyone's apps can be! My other writings and projects are scattered across the web, but can be found in the links page.

Contact me:

Signal: alp1n3.01 | Email Me | GitHub