Cursor is not code signed on mac?

Bug Report
1

I just installed the latest cursor build and when I start it from the CLI I get this error:
[0228/071301.229615:ERROR:codesign_util.cc(108)] SecCodeCheckValidity: Error Domain=NSOSStatusErrorDomain Code=-67062 "(null)" (-67062)

and when I check its code signing status, I see this:
$ codesign -v --verbose /usr/local/bin/cursor /usr/local/bin/cursor: code object is not signed at all

What’s up with this? What should I do about it?

Thanks.

2

Thanks for pointing this out!

Looking into this on our side.

Are you using Cursor or Cursor Nightly?

3

Did you download Cursor directly from https://cursor.sh or somewhere else?

4

I downloaded Cursor from cursor.sh, and I don’t think it’s the nightly - it’s the regular build.

FYI this started happening on my existing Cursor installation (I noticed it after installing an extension - Tailwind CSS).

I deleted the Cursor app from the Applications folder, then reinstalled it from the cursor.sh homepage.

The issue continued.

5

We currently do not sign the cursor CLI, only the main Cursor application at /Applications/Cursor.app/Contents/MacOS/Cursor. (VS Code also does not sign their CLI, if I’m not mistaken.)

6

The error just started happening though, I now see: [0228/071301.229615:ERROR:codesign_util.cc(108)] SecCodeCheckValidity: Error Domain=NSOSStatusErrorDomain Code=-67062 "(null)" (-67062) on my CLI whenever I type cursor, and last week and prior, I didn’t see this error.

Wondering what might have changed to cause it.

7

Opened a related topic here a while back, would appreciate a reply:

8

How do you sovle. I meet same problem in My Mac CLI when run cursor