See my fix above let me know if it helps temporarily
how did you create the HANDOVER? any tips?
I asked Cursor to write it. Something along the lines of āPlease write a comprehensive handover MD document outlining all progress completed so far with any specifics that another AI should know if they were to continue development. Be detailed.ā Or similar. I then added anything manually myself I thought it should know and reviewed it in depth before moving on.
Any news on this, my editor crashed as soon as i open it. Do you guys have any idea on how to solve/by pass it? im blocked 
It worked here, but letās see for how long. This needs to be fixed by CURSOR.
1 Like
I am using a MD file to write in work as I find the context typed in is lost too quickly. I havenāt tried opening in a new folder. I may try that next and will let you know. The MD file isnāt helping, sadly.
1 Like
It was terrible, I didnāt make any progress because he still doesnāt understand the context. This needs to be resolved otherwise itās useless after a few days of work.
I just gave it the handover doc, my initial project brief doc and development plan docs, got Cursor to read through all of it and then scan the project structure to completely understand the project. Iāve never had issues with context and understanding what to build next using this method.
Iām creating an online RPG webgame. So for my project itās complicated not to have the complete context because it generates a lot of errors in the process.
Ah yes I understand. That could be frustrating. I donāt think Cursor particularly handles long context very well as I assume it keeps it within local RAM (maybe to keep token costs down) or something. But I guess the context has to live somewhere, and I guess the trade-off of that is speed and in this case stability. I hope they fix it soon.
To ensure context is saved locally, a temporary solution is to configure Cursor to create a step-by-step context document that logs everything it does, allowing you to easily re-brief Cursor if needed.
I have the same bug, and I hope Cursor is planning to fix it.
Also, are there any files I can manually delete to stop Cursor from crashing?
I have also followed these steps. I will say in my case the switching to another folder by cloning my repo and simply moving to there helped more than the *.MD document.
As to the guy asking about that, rather than typing prompts into the chat box, type them into the *.MD and have the chat bot read it. Helps it keep context. That much is clear :).
The MD document is just to help with context continuation to a new chat with your Agent. The optimisation process is moving the project, clearing the chat and reopening.
I can say while the moving of the project did help, the problem creeps back. Iāve now had one crash in 16 hours since making the change. The IDE is still faster than before, but slowing noticeably. Iāll have to move folders again soon. This is clearly not a permanent solution.
No obviously its a workaround. As your project fills with more chat history the data has to be stored somewhere, Iām assuming RAM or something, causing it to slow over time.
This needs to be resolved urgently, it is something that tarnishes the name of the application. Who is going to pay for this? Itās complicated.
1 Like
Yeah, the problem is application data. On I canāt find it on my Ubuntu box, but I removed the folder, then recreated it and went back in and Cursor had my full chat history AND crashed immediately. So as this is VSCode itās doing something there in some way. Cursor should be able to provide how to work around this by simply restarting chat and clearing chat cache and it would be fine. Iām now on my third folder as two I can open and crash Cursor in under 10 seconds doing nothing.
I found a way here that is working for now, but itās all a hack and the cursor needs to fix this urgently. Iāve been going to the top right side and deleting the oldest chats from the context. It gets in the way a bit, but if you do this and have a backup of it summarizing the context and inserting it right away, it seems to be less work and itās working here.
Now crashes faster and more often.
Will there be a fix for this soon?