Without changing anything in my setup, the composer automatically started changing my files, sometimes multiple, breaking existing features and changing API keys, instead of making suggestions to be accepted. it has a mind of it’s own. Is this a setting somewhere to automatically accept? I didn’t change any settings, this is my first time using cursor.
Create a rule in
cursor rules that satisfies version control/backups and have it start everything by first creating a .bak of each file it touches, or include a documentation changelog diary etc…
Its still a FN Infant Bot – so its going to take some learning curve on how to wrnagle these things.
Once we understand how to properly direct their behavior to a discreet and reliable granular level - it will always be a helper tool, and now a full blow “junior devops engineer”
Also - ensure that you tell it that it cannot delete files automatically - and in your YOLO settings put certain commands on the blacklist, like RM del, delete, or even mv, move. etc…
When it wants to do any of those functions - it awaits human input.
This is great, thank you for the tips.
This is just a for fun project. I decided to try to check out cursor so there’s been no disaster and the errors have helped me learn some tools
better anyway.
The initial spin up was quite fun to watch and I was so shocked when it got a full stack site up pretty quickly. But now that I’m more specific in what I wanna do I have to be much more directive like you described. I appreciate your help.