Cursor-cli installation method zsh vs bash

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

macOS Tahoe with M chips.

The current bash install instruction also cause the Homebrew installation to malfunction. Install using:

brew install cursor-cli

This will trigger a macOS security prompt for file_service.darwin-arm64.node, markle-tree-napi.darwin-x64.node, and rg.

Same issue with:
curl https://cursor.com/install -fsS | bash

It’s working well now with:
curl https://cursor.com/install -fsS | zsh

Reference:

Steps to Reproduce

brew install cursor-cli

curl https://cursor.com/install -fsS | bash

Operating System

MacOS

Version Information

CLI Version 2026.04.17-787b533
Model Composer 2 Fast
Subscription Tier Team
OS darwin (arm64)
Terminal warp
Shell zsh

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey! Thanks for creating this thread (and for the thorough report, including the discovery that zsh works as a workaround).

This is a confirmed issue on our side. The CLI native binaries are properly signed but not fully verified by macOS Gatekeeper in certain install scenarios, which triggers the security prompts you’re seeing.

Workaround (in addition to the zsh method you found): After installing, you can strip the macOS quarantine flag from the CLI files:

xattr -cr ~/.local/share/cursor-agent/

For Homebrew installs:

xattr -cr /opt/homebrew/Caskroom/cursor-cli/

You only need to run this once per install or update. You may also find this related thread helpful, where another user reported the same class of issue.

We’re aware of this and working to address it in the install process. Let me know if the workaround resolves it for you!

1 Like