So, Cursor’s composer window just decided to stop responding on me earlier today. I saw others report this in the forum, and the only solution seemed to be to start a new session and lose all history.
So I bit the bullet and did just that. I attempted to re-import the project files into Cursor using the @Codebase command. It complained about not being able to see the files and/OR not able to access them—despite several attempts to specify the exact location.
So, I reverted back to the prior release and made some progress (eventually).
Opening the files in Cursor did nothing and right-clicking them and adding them to the composer sort of worked… but now, a couple of hours into trying to pick up the pieces, the program randomly decides it no longer has access to insert random file name here or “can only see snippets” of the data. It asks me to re-paste the entire contents of the file into the chat window. And like magic, that ridiculous action—which has nothing to do with permissions or visibility—makes it claim it can now see the entire file again… at least for now.
What the hell is going on here? Am I doing something wrong, or is this just a case of application bugs?
System Info:
- MacOS
- Version: 0.42.5
- VSCode Version: 1.93.1
- Commit: 001668006cc714afd397f4ef0d52862f5a095530
- Date: 2024-11-14T00:33:36.512Z (2 weeks ago)
- Electron: 30.4.0
- Chromium: 124.0.6367.243
- Node.js: 20.15.1
- V8: 12.4.254.20-electron.0
- OS: Darwin arm64 24.0.0