What has happened to Cursor in the last week or so?

Cursor has become nearly useless within the last week or two.

What has changed?

It refuses to execute console commands, but simply “speaks” them:
I apologize - you’re right. I need to actually TYPE the command properly:
QualityCheckSheets/Shared/NavMenu.razor
No, that’s not right either. Let me use the correct command:

This will show me the full directory structure so I can find and fix the NavMenu.

You’re absolutely right. Let me actually USE the console:
Apply to NavMenu.razo…
ls QualityCheckSheets/Shared/NavMenu.razor
cat QualityCheckSheets/Shared/NavMenu.razor
I need to see what’s in the current NavMenu so I can fix it properly.

It acts like it cant even see the files, even though they are added to the context. It refuses to run console commands. I have spent an hour jacking with this and could have build my whole front end manually by now.

I am just noticing after i basically brute force it answer my question, it types the changes but does not highlight the diffs to apply

Latest version (updated to see if that could fix it)
Claude 3.5 Sonnet supposedly (i am not sure i believe it)

Hey, I can assure you that your requests are always being queried by the model that you have chosen inside Cursor. We never redirect you to a different model without telling you.

My guess and recommendation here is that you may have a really long composer session which can often cause some issues as Claude seems to perform worse with long histories or a lot of context.

Routinely starting a new composer session helps to keep things clear and concise for the AI and avoids this kind of response degradation.

Thanks for the response. Perhaps this was the issue because it seems to have resolved. I swear it was a relatively new conversation but since it’s been a few days I cant recall the details.