I’ve been using cursor a lot for the last 3 weeks. I’ve reached a point in my project where I’ve had to start a new chat multiple times and re-teach it about my project. Those times though were due to the bug in previous versions where it would just get stuck on generating forever.
Now I have bigger issues of significant hallucination or dementia. It is quite dangerous because it will decide to start down a different path subtly and only after multiple revisions across multiple files does it become apparent that it has fundamentally forgotten about some methods/ system we put in place only ~10 minutes earlier.
My question is - is this just a function of keeping your composer chat going for a long time - i.e. the variance increases over time and gets to a point where literally from one ‘prompt’ to the next it might significantly hallucinate?
I’m trying to learn how to get the most out of cursor, for 99% of the time using composer to date (maybe 6 hours a day for 3 weeks) it has been pretty much perfect, but now it’s extremely bad/ dangerous.
For me its been every feature gets a new composer. Like you mentioned if i let the context get too big Composer starts to really make questionable choices.
Also I am pretty specific with what i want using composer. I explain my problem or bug in detail then say i want to use X,Y,and Z to solve this issue here is the docs for these then link to docs.
Most of the issues i see on the this forum are people being way to vague like “build me an app”, or “I have a bug”. Remember this is a tool its only going to be successful if you allow it to be.
The hallucination is becoming insane now. It will straight up mix a new function into an existing one rather than create it as a separate function in the code - two completely different functions that in no way should be related.