Bug: Cursor port 8080 causes massive problems, please move the port or issue a warning when the agent has a connection issue

Describe the Bug

Why choose port 8080? A LOT OF SERVERS USE THIS AS A DEFAULT

This causes the agent to see a server when it shouldn’t and attempt to debug and possibly kill it’s own connection.

I suggest choosing a much high port, or at least update the warning that says you might be using a vpn connection to include the possibility that there is a port running on 8080 and this is reserver for cursor

Steps to Reproduce

Make a server run on 8080. And have the agent kill it, then watch as the connection is lost and you get a vpn warning.

Expected Behavior

A server should be able to run on 8080 without curser being affected.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

1 Like

I am facing the same issue. Please let me know how to stop cursor from using port 8080.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.