macOS My Machines: --computer-use keeps worker up but Shell returns no exit status (CLI 2026.09.15)

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Follow-up to the macOS --computer-use / signed SEA createRequire crash that was marked fixed in CLI 2026.09.08:

On our Apple Silicon Mac (My Machines worker), we are on CLI 2026.09.15-d2fe57e (agent update reports already up to date). The old Filesystem createRequire is disabled in the self-contained worker SEA crash does not reproduce: with --computer-use, the worker stays running and Computer Use debug can show Ready.

However, enabling --computer-use breaks the agent Shell tool:

  • Worker with --computer-use: Shell calls return no exit status (even trivial echo). We labeled this SHELL_STILL_DEAD in our probes.
  • Same machine / same --worker-dir / same LaunchAgent without --computer-use: Shell works (SHELL_OK).

So this is a different manifestation / regression after the 09.08 fix: CU no longer crashes at start, but Shell/exec channel dies while the worker remains up.

Workaround we use today: LaunchAgent without --computer-use for coding/Shell; Simulator UI via XcodeBuildMCP + simctl (no XCUITest).

Steps to Reproduce

  1. Apple Silicon Mac on macOS 27 Golden Gate (latest); Cursor CLI 2026.09.15-d2fe57e.
  2. Install/grant Cursor Computer Use.app; Accessibility + Screen Recording on. agent worker debug can show Computer use Ready: yes.
  3. Start the My Machines worker without CU and confirm Shell:
    agent worker --worker-dir /path/to/repo start
    → agent Shell echo hello → exit 0 / SHELL_OK.
  4. Stop the worker. Start the My Machines worker with CU:
    agent worker --computer-use --worker-dir /path/to/repo start
    → worker stays up (no createRequire abort).
  5. Run agent Shell echo hello again.
    → no exit status / SHELL_STILL_DEAD.
  6. Remove --computer-use, restart → Shell OK again.

(Also reproducible under launchd LaunchAgent with/without the --computer-use ProgramArgument.)

Expected Behavior

--computer-use worker stays healthy and Shell/exec-daemon keeps working (screenshots/clicks + Shell).

Operating System

MacOS

Version Information

  • Cursor CLI: 2026.09.15-d2fe57e (agent update: already up to date)
  • Related prior fix: 2026.09.08 for createRequire SEA crash (linked thread above)
  • Worker: My Machines worker
  • Computer Use.app present; debug Ready yes after permissions
  • OS: macOS 27 Golden Gate (Apple Silicon)

Additional Information

  • Bisect: only flipping --computer-use changes Shell from OK → dead.
  • Do not set CURSOR_AGENT_ALLOW_UNSIGNED_COMPUTER_USE=1 (known to fail CUCursorService team-id gate).
  • Happy to attach worker stdout/stderr / agent worker debug if useful.

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @Mohamed2, thanks for the report and the clean A/B - that pins it down.

We’ve reproduced this on our side; it’s an issue we’re tracking, and nothing on your end. For now, keep the no---computer-use LaunchAgent for coding and Shell work (and you’re right to skip CURSOR_AGENT_ALLOW_UNSIGNED_COMPUTER_USE=1 - it won’t help here).

I’ll post here when there’s a fix; agent update will pick it up.

9

Hey @Mohamed2,

Quick update: a fix for the Shell tool returning no exit status on --computer-use workers has landed and will be included in an upcoming Cursor CLI release.

Until then, your current setup (the LaunchAgent without --computer-use for coding and Shell work) is still the right call. Let me know if you still hit it after updating.