Remote agent Waiting for worker forever

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When trying to create an agent with remote control, a message waiting for worker is diplayed forever.

Steps to Reproduce

create an agent with remote control

Expected Behavior

agent created

Screenshots / Screen Recordings

Capture d’écran 2026-08-09 à 17.32.17.png
Capture d’écran 2026-08-09 à 17.32.17.png630×422 20.5 KB

Operating System

MacOS

Version Information

Version: 3.15.6
VS Code Extension API: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
Date: 2026-08-06T01:41:03.876Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hey @clakech - thanks for the report. That hang isn’t intended.

Fully quit Cursor (Cmd+Q), open your main qima-platform project window (not just a worktree / Agents Window), keep the Mac awake with Remote Control on, and try again. If it still sticks, quit, run pkill -f cursor-agent-worker, reopen only that project, and retry - or pick a machine that shows as connected, or run in the cloud.

Same class of issue as this related thread. We’ve let the team know and this is an issue we’re tracking - I’ll post here when there’s an update.

7

me too

8

I’m using Cursor Pro on macOS Apple Silicon.

  • Cursor version: 3.15.6
  • Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
  • OS: Darwin arm64 25.5.0
  • Plan: Pro
  • Layout: Agents Window

Remote Control remains stuck at:

Setting up environment
Waiting for a worker

The project is a valid Git repository:

  • Branch: main
  • Has an initial commit
  • origin remote is configured
  • Local branch is synchronized with origin/main

I have already tried:

  • Enabling Remote Control in the Agents Window
  • Keeping the Mac awake and online
  • Fully quitting and restarting Cursor
  • Opening only the main project workspace
  • Running pkill -f cursor-agent-worker
  • Starting a new Remote Control session

The issue persists. Is this a known bug in Cursor 3.15.6? If so, which Cursor version contains the fix?

9

the same