Thanks. All 4 Request IDs you sent had Privacy Mode enabled. This greatly limits our ability to see what went wrong on the backend.
If you can, please try temporarily turning off Privacy Mode (Cursor Settings > Privacy Mode) and reproduce the issue. After that, send a new Request ID. This will help the team investigate.
If you can’t turn off Privacy Mode, we need info from my previous questions:
Errors in Developer Tools (Help > Toggle Developer Tools) - open the console before the agent hangs
Approximate size of the codebase (how many files?)
Does the bug reproduce in a new empty project?
Regarding credits, if the requests are truly stuck and haven’t completed, they usually aren’t deducted, but we can check more accurately with the Request ID. Once you send a working ID (without Privacy Mode), we can take a look.
Likely the update messed with how it handles file parsing, causing those indefinite hangs from overload or bad caching. Suggestion: Roll back to the previous version if you can, or limit the scope to fewer files per query might unstick it for now.
When will cursor finaly be usable again? Its time for a statement of the cursor ceo about all these issues that dont get fixed and new ones getting created
I was able to fix the issue by removing Cursor completely and reinstalling again. But even when I tried to reinstall I kept getting errors like “Cursor is damaged and can’t be opened. You should move it to the Trash.” This seems to be a typical errors on macOS reported by many Cursor users.
So after a full removal, reboot Macbook and reinstall again it was all fixed.
