Hello!
I’m have been using cursor for multiple projects now and the longer I use the harder it gets sometimes for it to get the work done.
We are about the 4-5. project and now it’s even hard for it to set up the evironment and dependecies as half of the command lines are not working properly and run to an error.
An other problem is that sometimes when I work on a project, cursor just wants to ehck a file in another project folder and make the dependency files there. I explicitly say what is the project root folder we are working in, and even if it is on C drive, it just wants to check the package.json in another, previous project on D drive.
One last problem is that cursor sometimes can’t check or open file when it’s clearly there, even it finds it in file listing but runs to an error in opening it.
Do you have an solution for these problems? Maybe I should clear cursor cache?
Thanks in advance.
Hey,
My best recommendation is to frequently start a new composer session every time you move to a new area of your code, or start work on a new feature.
When your composer chats get too long, and full of context, the LLM can start to degrade quickly in the performance of its outputs. LLMs work best when given precise information, only relevant to the task at hand, but long composer sessions would contain all the history in each message, which does often not work well.
Hope this helps!
Hello @danperks !
Thanks for your response! I was doing that already and starte every chat with saying what is the project folder we will work in like “C:/Users/XY/XY folder” and this is mainly why I’m surprised in wants to navigate to an another project folder on another disk.
Anyway maybe I found something that could help. As you can see, I used quotation marks, but if I used apostrophe today, it could navigate easier between the folders. Maybe I just had some luck now.
Glad you are making progress! You are not the first to be in a similar situation, and it’s a workflow we hope to improve on in the future!