Cursor agent segfaults due to CA mismatch

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

agent -f segfaults on launch. Same as this thread, the bug was never fixed: Cursor Agent Segfaults on Launch? - #5 by yush_g

This is the fix:

      22 -exec -a "$0" "$NODE_BIN" --use-system-ca "$SCRIPT_DIR/index.js" "$@"
      22 +# REASON: --use-system-ca causes segfaults on macOS. Removing it fixes "zsh: segmentation fault" on launch.
      23 +exec -a "$0" "$NODE_BIN" "$SCRIPT_DIR/index.js" "$@"

Steps to Reproduce

agent -f with my system certs.

Expected Behavior

Not segfault.

Operating System

MacOS

Version Information

Latest.
$ agent --version
2026.03.20-44cb435

Does this stop you from using Cursor

Yes - Cursor is unusable

4

Hey, thanks for the follow-up report. I can see this issue has been around since February and still hasn’t been fixed. That’s frustrating.

I’ve passed it on to the team. For now, the workaround is still the same, remove --use-system-ca from the launcher script after each update. I know that’s inconvenient.

I’ll post an update here if there’s any news on a fix.

9

Hey @yush_g,
Sorry for the silence here. We made a change in this area! The launcher now skips --use-system-ca automatically when it would crash on macOS. Could you reinstall the latest cursor-agent and try agent -f again? Let us know in a new thread if the segfault on launch still happens.