I’m working now, I have a lot of chats in the composer. And if I change the folder name and open the cursor again, the history disappears. Make it memorize somehow inside the folder.
The same applies to changing the working servers when moving the project.
This is unlikely, but I can give you a piece of advice. There’s no need for Chat to remember what you did before. I have a much better solution that yields better results.
Start your project and instruct the Chat section – “Not Composer, but the Chat section” – to thoroughly analyze your project, divide it into 4 or 5 phases, and create a roadmap for each phase. If you ask it to write this as a TXT file, it will present it in a table format which is much clearer and more understandable.
In the main directory of the project, create a text file named “.roadfaz” and copy the roadmap you received from Chat into this file.
Whenever you shut down your computer, go to the Chat section (or “Cursor”) and write the following prompt:
“Analyze the project in detail and in depth, thoroughly understand the project, review the .roadfaz file, and list the remaining tasks.”
Attach the “.roadfaz” file to Chat and run it as @codebase.
After this process, the Cursor will scan your project, list the missing parts and important points, and again save this as a TXT file.
The next day, when you start working, add the “.roadfaz” file to Composer so that it can deeply examine the project and continue according to the .roadfaz roadmap.
Roadmap is your main road, roadfaz is your next stage. Also, don’t forget that when you work on the same page for hours, Cursor’s “brain” overheats. It starts writing strange codes and throws errors.
When you follow this method, Cursor works much more efficiently.
Thanks for the feature suggestion. This isn’t the first time we’ve had this feature suggested as users quite often need to restructure or rename the path their codebase is in.
I’ve added this is to our internal feature tracker so hopefully we can get this added in a future update.