# macOS My Machines: --computer-use keeps worker up but Shell returns no exit status (CLI 2026.09.15) **URL:** \ **Category:** Bug Reports\ **Tags:** cli, terminal, macos, computer-use\ **Created:** [September 18, 2026, 2:53am UTC](https://forum.cursor.com/t/macos-my-machines-computer-use-keeps-worker-up-but-shell-returns-no-exit-status-cli-2026-09-15/172097 "2026-09-18T02:53:02Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Mohamed2](https://avatars.discourse-cdn.com/v4/letter/m/c5a1d2/32.png) [@Mohamed2](https://forum.cursor.com/u/Mohamed2)\ **Post date:** [September 18, 2026, 2:53am UTC](https://forum.cursor.com/t/macos-my-machines-computer-use-keeps-worker-up-but-shell-returns-no-exit-status-cli-2026-09-15/172097/1 "2026-09-18T02:53:02Z")
### 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`: > [@macOS self-hosted worker, \`agent worker --computer-use start\` crashes at startup](https://forum.cursor.com/t/macos-self-hosted-worker-agent-worker-computer-use-start-crashes-at-startup/170703): > > Where does the bug appear (feature/product)? Cursor CLI Describe the Bug This has been tested only on an Intel Mac with Tahoe. On a macOS self-hosted worker, agent worker --computer-use start crashes at startup. The worker re-execs into the signed worker binary (cursor-agent-worker-sea), which immediately aborts with: Error: Filesystem createRequire is disabled in the self-contained worker SEA Without --computer-use the worker starts and runs fine. So computer use is unusable on macOS. Root… 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 ---
**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\ **Post date:** [September 18, 2026, 8:11am UTC](https://forum.cursor.com/t/macos-my-machines-computer-use-keeps-worker-up-but-shell-returns-no-exit-status-cli-2026-09-15/172097/7 "2026-09-18T08:11:01Z")
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. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 20, 2026, 9:10am UTC](https://forum.cursor.com/t/macos-my-machines-computer-use-keeps-worker-up-but-shell-returns-no-exit-status-cli-2026-09-15/172097/9 "2026-09-20T09:10:30Z")
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.