Cursor CLI agent worker start keeps reconnecting to bridge on macOS, with or without proxy

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

agent worker start starts normally, but the worker never establishes a stable bridge
connection. It repeatedly reconnects and does not become usable.

Important note:
I tested both with proxy environment variables present and with proxy variables removed. The
behavior was the same in both cases, so this does not appear to be caused only by proxy
settings.

What I see:

  • worker mode starts normally
  • working directory is detected correctly
  • repository metadata is detected correctly
  • user privacy mode is fetched successfully
  • exec-daemon starts
  • bridge switches from https://api2.cursor.sh to https://api2direct.cursor.sh with host
    header api2.cursor.sh
  • after that, it loops on reconnect

02:35:00.235 INFO  Session state after connect ctx=worker-mode meta={state: "connecting"}
02:35:00.235 INFO  Starting to iterate over stream frames ctx=worker-mode
02:35:10.999 INFO  Starting bridge connection attempt ctx=worker-mode meta={retryCount: 28}
02:35:11.000 INFO  Session state before connect ctx=worker-mode meta={state: "idle"}
02:35:11.000 DEBUG Setting host header for ALB routing ctx=worker-mode meta={hostHeader: "api2.cursor.sh"}
02:35:11.000 INFO  Session state after connect ctx=worker-mode meta={state: "verifying"}
02:35:11.000 INFO  Starting to iterate over stream frames ctx=worker-mode
02:35:21.588 INFO  Starting bridge connection attempt ctx=worker-mode meta={retryCount: 29}
02:35:21.588 INFO  Session state before connect ctx=worker-mode meta={state: "idle"}
02:35:21.588 DEBUG Setting host header for ALB routing ctx=worker-mode meta={hostHeader: "api2.cursor.sh"}

Steps to Reproduce

agent worker start

Operating System

MacOS

Version Information

2026.03.25-933d5a6

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, thanks for the detailed report.

Quick clarification: agent worker start (private workers) is currently an enterprise/team feature and isn’t available on Pro plans. The issue here is that the CLI doesn’t give a clear error message about this. Instead, it falls into an infinite reconnect loop, which is obviously not great UX.

The team is aware of this gap in error handling. Your report helps increase visibility on this.

If you’re looking for cloud-based agent execution on a Pro plan, you can use Cloud Agents instead: Cloud Agents | Cursor Docs. They’re available through the Cursor web interface, desktop app, or via integrations like Slack or GitHub.

Let me know if you have any other questions.

5

I am getting this error, and I am on the team plan

6

https://x.com/ericzakariasson/status/2037146278979629361 only works on teams plan ? that sucks…