Skip to content

[Discussion]: No write permission #639

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 tasks done
huuthiendev opened this issue Apr 15, 2025 · 6 comments
Open
3 tasks done

[Discussion]: No write permission #639

huuthiendev opened this issue Apr 15, 2025 · 6 comments
Labels
question Further information is requested

Comments

@huuthiendev
Copy link

huuthiendev commented Apr 15, 2025

Issue Checklist

  • I understand that Issues are used to provide feedback and solve problems, not to complain in the comments section, and will provide more information to help solve the problem.
  • I confirm that I need to raise questions and discuss problems, not Bug feedback or demand suggestions.
  • I have read Github Issues and searched for existing open issues and closed issues, and found no similar issues.

Platform

macOS ARM64

Version

1.9.05

Your question

I'm running macOS and having this problem whether selecting option 1 or 10. I have already run the script in sudo mode. How can I solve it?

Image

Additional information

Priority

High (It blocks my work)

@huuthiendev huuthiendev added the question Further information is requested label Apr 15, 2025
@rudra-sah00
Copy link

I also faced the same it't not actually changing the machine id but it generates a new machine id but it does not have sufficient permission to write that in cursor.app

@Mikazuki016
Copy link

I have also encountered this issue. I saw that the official solution requires running with administrator privileges and setting a certain file to readable, but the documentation does not specify which file.

@rudra-sah00
Copy link

❗️ macOS System Integrity Protection (SIP) Warning

The issue is due to macOS System Integrity Protection (SIP).

  1. SIP prevents modifications to system-protected app bundles (like Cursor.app inside /Applications).
  2. Even with sudo, you cannot write to certain directories unless SIP is disabled, or you move the app outside /Applications.

Solution
You need to temporarily disable SIP:

  1. Restart your Mac and boot into Recovery Mode (hold Command + R at startup).
  2. Open Terminal from the menu bar.
  3. Run:
    csrutil disable
    reboot

@canmi21
Copy link
Contributor

canmi21 commented Apr 15, 2025

sudo

@rudra-sah00
Copy link

sudo

still not working
Even with sudo, you cannot write to certain directories unless SIP is disabled, or you move the app outside /Applications.

@Pasithea0
Copy link

Yeah, none of the solutions work. Please add a app config so we can move Cursor outside of the apps folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants