# Cursor-cli installation method zsh vs bash

**URL:** <https://forum.cursor.com/t/cursor-cli-installation-method-zsh-vs-bash/158601>\
**Category:** Bug Reports\
**Tags:** cli, installation, macos\
**Created:** [April 21, 2026, 7:02am UTC](https://forum.cursor.com/t/cursor-cli-installation-method-zsh-vs-bash/158601 "2026-04-21T07:02:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abner\_Shang](https://avatars.discourse-cdn.com/v4/letter/a/848f3c/32.png) [@Abner\_Shang](https://forum.cursor.com/u/Abner_Shang)\
**Post date:** [April 21, 2026, 7:02am UTC](https://forum.cursor.com/t/cursor-cli-installation-method-zsh-vs-bash/158601/1 "2026-04-21T07:02:39Z")

</div>

### 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:

> [@Cursor-agent 2026.04.16-2d20146: Cannot find module '@anysphere/file-service-darwin-x64' on Intel Mac](https://forum.cursor.com/t/cursor-agent-2026-04-16-2d20146-cannot-find-module-anysphere-file-service-darwin-x64-on-intel-mac/158256/16):
>
> Hi, I have the same problem on a macbook pro m2, not intel. EDIT : default install is curl [https://cursor.com/install](https://cursor.com/install) -fsS | bash while mac use zsh by default, doing so works for me : curl [https://cursor.com/install](https://cursor.com/install) -fsS | zsh

> [@Cursor-agent 2026.04.16-2d20146: Cannot find module '@anysphere/file-service-darwin-x64' on Intel Mac](https://forum.cursor.com/t/cursor-agent-2026-04-16-2d20146-cannot-find-module-anysphere-file-service-darwin-x64-on-intel-mac/158256/20):
>
> macOS Tahoe with M chips. This is the fix! It worked for me too! 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. It’s working well now with: curl [https://cursor.com/install](https://cursor.com/install) -fsS | zsh

### 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

---

<div class="post-metadata">

**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:** [April 21, 2026, 10:51am UTC](https://forum.cursor.com/t/cursor-cli-installation-method-zsh-vs-bash/158601/6 "2026-04-21T10:51:03Z")

</div>

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:

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

```

For Homebrew installs:

```auto
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](https://forum.cursor.com/t/cursor-agent-merkle-tree-napi-darwin-arm64-node-not-opened/155056) 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!

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [May 28, 2026, 2:16pm UTC](https://forum.cursor.com/t/cursor-cli-installation-method-zsh-vs-bash/158601/9 "2026-05-28T14:16:11Z")

</div>

Closed on May 28, 2026, 2:16pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.