Cursor UI and agent not working

Support Bug Reports
1

Describe the Bug

I’m on a MacBook Air M2 (running macOS 26 beta 2), and Cursor is basically unusable for me right now. The agent/chat doesn’t work at all.

Here’s what happens:
• When I type something into the agent input and hit Enter, the text just disappears instantly. No reply, nothing.
• Every time I quit Cursor, it shows “Discarding backups is taking a bit longer…”
• The ~/Library/Logs/Cursor folder doesn’t exist. So there are literally no logs being generated.

What I’ve tried so far:

  1. Fully deleted and reinstalled Cursor (app, caches, saved state, preferences, everything)
  2. Confirmed Node and TypeScript are installed and working (node -v = v22.16.0, tsc -v = 5.8.3)
  3. Cleared TypeScript and related caches
  4. Tried sudo xattr -rd com.apple.quarantine /Applications/Cursor.app to remove quarantine flags, but Terminal was blocked from modifying apps by macOS
  5. Gave both Terminal and Cursor Full Disk Access in System Settings
  6. Rebooted, reinstalled again, opened a new blank .ts file — same result

Still no luck. Agent input doesn’t work, nothing shows up, and no logs are generated. I’m assuming the agent process is silently failing or being blocked by something in the macOS 15 beta (maybe SIP or some new sandboxing stuff?).

Thanks.

Steps to Reproduce

Im not sure, because I was doing things as normal. I think I started to make new chats since the request took such a long time to process.

I think what may have influenced was modifying the node modules? Because there was an error with npm run dev, I requested it to fix it, and because it took such a long time to resolve it, I kept on stopping the request in the middle, then restart a new one, over and over.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.2 (Universal)
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:07:27.002Z (1 day ago)
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
2

Same here

Version: 1.2.2
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:08:52.104Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0

3

When you clicked new chat, did you actually use it? From the video you clicked new chat, then tried to restore an old chat that maybe too full.

4

Yes, same with me - Cursor is unusable for at least a week.

5

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