First, cursor is awesome. Great product. Thank you Cursor folks.
In the last weeks though, it looks like the Cursor prompting has been getting to eager to:
- Just generate lots of code, shoot first ask questions later, make it compile even if it does nothing like the prompt.
- Lost in the middle issues are becoming more and more frequent, even with simple prompts, such as, replace this constant with a state, it adds a ref.
- Claude 3.7 has become useless in Cursor, at least in our environment. It kind of stopped getting anything right a few weeks ago.
Some times, a bit of half baked code that has the right concepts is better than nonsense that compiles and does nothing of that it is supposed to do, and it looks like that is the current direction. I’m suspecting your backend injected instructions are getting too long, or complex, or contradictory (potentially with something the end user developer is trying to do).
What this is causing is having me and my team use cursor less and rely more on other tools or the API to generate code. Maybe a vibecoder mode would help the cause (that I can turn off), or having more knobs and switches to control what behavior we’re getting out of the agent.
Thoughts?