This was so true. I have lost 1 day of work because of this. I can’t fixating working code blocks (php so no rocket science). So the modulair approach is not well trained. And there is a sense of it all
Curious, how do you handle this?
Revert using source control and re-prompt or do you try to massage whatever it left you with?
I find the errors where it’s not thinking far enough ahead cause me the biggest headaches. A lot of hand holding is required but I’m becoming a better programmer through this.
1 Like
"Revert using source control and re-prompt "> best.
I also play with different terms, try a different perspective, focus on this first en test with me till this is handled correctly… then tidy up, make it modular, separate code into different scripts instead of one file with 5k rows.
But I agree you learn with the system, truly creative coding.
Makes me want to draw again for functions, methods, classes back in the days i played with Java at university (i’m 51 haha)…
So i want to draw the outline of a script or code, designing first (architecture) and then build this logically or explorer effective low cpu alts…
though time consuming…
1 Like
I agree that it’s very creative. I’m retired, started programming in assembly in 1980, but this is a lot of fun although in a different way. A lot less hunting for documentation and more thinking about what I want to do. Cheers.
1 Like
You can disable auto-update, but weirdly enough it forces an update to .46 when it makes that change…but then after re-installing .45 it’s okay.
1 Like
thx will try that! I guess the Cursor team is swiftly updating these issues.
LOL, great ! I have a ZX Spectrum/ Commodore 64 basic start. Yet coming from poor single parent background I was fortunate enough working with computers at school due a university partnership (terminal server/client) mac plus etc etc
Registered, and came here to say this, the new version is overcomplicating a simple UX process and buggy as ■■■■. I’ll be reverting to 0.45
1 Like
something is destroyed… i came with Version 0.45 and claude 3,7. it was awesome it did exactly what i wanted. not too much not to less. but now after the update i cant even fix a simple react formular… it gets worse it makes new errors and when trying to fix it creates new functions, but doesnt delete the old useless ones… the code gets bigger and bigger instead of fixing some lines…
please any reaction from cursor team?
2 Likes
I’ve been tracking these forums for months and always found myself baffled by people’s claims that cursor was getting worse. I’m now on board. 0.46 cannot do the simplest things that it used to have no problem with.
Edit: I just downgraded to 0.45 and it one-shotted the solution that 0.46 simply could not solve. It wasn’t a particularly hard problem. I’m so confused.
3 Likes
Im waiting for anyone from Cursor to reply, finding more and more bricked parts on each update but not received a single response to bug reports
2 Likes
beware to remove all preferences/support file. Cursor will trigger a fresh install setup… go 0.46 workin again on my macbook arm64 m3 max
i tried with 0.45… it dieas auto update everytime to last version. and as long i dont restart the composer is broken and does not generate. it stopps everytime instant… how you all managed to run the old version?
Sonnet 3.7 goes OFF the rails, so insanely off the rails it’s unusable.
1 Like
yes, I agree, prefer claude 3.5
1 Like
One really has to keep Sonnet 3.7 on a tight leash, but the output product has been stellar. Make sure you save the simple tasks for lesser models, and your Docs indexing is loaded with the right sources.
The Cursor Dev’s obviously doing their best with these rapid fire updates, and I am accepting all of them. Keep it happening boys this is an Amazing ride !
Maybe just me, but I didn’t see any of this.
We do keep our files small in size and scope intentionally so which always has helped keep it from overmodifying.
That said I have a full .cursorrule file in place as well with persona, project annotations, how it should approach problems by checking the files first every time, how it should use linear thinking or even the Sequential Thinking MCP to formulate its plan of action etc.
I think 3.7 can go off the rails as some pointed, but given I’ve seen several comments suggest defined rules files are what they think works, and I am seeing exact same thing with similar style .cursorrules file, it likely is that simple.
Maybe cursor latest removed some default prompt parts when they merged the 2 modes & changed automated context detections.
1 Like
What does your main cursorrules file look like? Do you provide any baseline instructions?
We tell it for example to always check the files first and confirm its findings, keep changes small, don’t remove comments.
We also give it persona and project domain knowledge, tell it to utilize tools like MCPs explicitly etc.
Cursor version 0.46.8 on windows is now completely unusable with “oom” error crashing my cursor instance with a high frequency …