Cursor composer in newst version is complete mess

Bug Reports
1

I’ve been using Composer for a couple of days, and everything was working fine until today.
Today’s version has issues with using tools – it either doesn’t edit files at all or displays strange errors.

image
image1080×674 70.6 KB

image
image1076×200 23.8 KB

in english he says: “Sorry, it looks like I’m having an issue with the editing tools. Let’s try a different approach – instead of trying to edit the entire file, let’s focus on specific changes.”

image
image1090×362 38.8 KB

in english: “Sorry, but it looks like I’m having a serious issue with the editing tools. May I suggest that we:”

Can you add an option to choose between a couple of cursor versions, please? Right now, it’s a lottery – you never know when a new version will break your workflow. You’re releasing too many buggy versions too often.

Version: 0.45.9
VSCode Version: 1.96.2
Commit: cce0110ca40ceb61e76ecea08d24210123895320
Date: 2025-02-02T06:44:49.761Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin x64 23.5.0

2 Likes
2

Potentially the same problem as here: 🚫 Cursor is not updating the code

3

Hey, which model are you using?

Some models have better ability to call tools than others, like o3-mini for example is not great at it, but all the LLMs can get themselves into situations where they confuse themselves around tool call formatting, and are unable to call upon tools from that point onwards.

My recommendation would be to state a new, fresh composer session and, if helpful, you can @ the old composer session as context to get up and running quicker!