Hi, thanks for reporting an issue with Cursor.
Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.
If you have done so, please check this box.
on
Describe the Bug
Last night, I was coding away like a lit-up Christmas tree – Composer and I were in sync, and the program just kept improving.
It was great! But all good things must come to an end, and it did last night… again.
This isn’t the first time Composer has failed, and I really hope they prioritize fixing this bug because it’s incredibly frustrating.
The most annoying part is that even if you press Ctrl-N to start a new conversation, Composer loses its memory.
It forgets everything, forcing you to explain everything from scratch, reconfigure all the related files, and guide Composer
back to finding the common thread.
It’s exhausting, time-consuming, and you can’t even be sure it’ll work properly.
On top of that, you have to set up git and remember to use it proactively,
just in case things go south again, and it will !!
Steps to Reproduce
you just have to use composer for a while with many files and that major corrections have to be made
that composer itself suggests in the program then it will certainly end in a bad way
Expected Behavior
That I was told as usual that something had been done like this and that
after composer had fixed the problem in his brain and whether I could
accept this or not, but no composer thinks and thinks and thinks
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version : 0,43,6
VSCode Version: 1.93.1
Additional Information
Windows 11 V24H2 Build 26100.2605
Does this stop you from using Cursor
Yes - Cursor is unusable