Worker start does not start

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

I run cursor worker start and it never starts

Steps to Reproduce

Run cursor worker start

Expected Behavior

The worker starts and shows up under ‘my machines’

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.22.12
VS Code Extension API: 1.128.0
Commit: 3a92974361033b2051526321308c2740fe5912c0
Date: 2026-09-26T04:55:12.125Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @lonny, thanks for the report!

The worker command is part of the Cursor Agent CLI, not the cursor editor command. cursor worker start gets passed to the editor, so Cursor opens and no worker is started.

Could you try this instead:

  1. If you haven’t installed the Agent CLI yet, run curl https://cursor.com/install -fsS | bash
  2. Sign in with agent login
  3. cd into the project folder you want your agents to work in
  4. Run agent worker start (or cursor agent worker start) and leave that terminal open

After a few seconds your Mac should show up under My Machines. If it doesn’t, please reply with the output of agent worker start --debug and your agent --version.

Setup guide: My Machines | Cursor Docs

Thanks this worked.

FYI it was the cursor agent who told me to run cursor worker start, not agent worker start. So I think both myself and cursor were confused.