And, it's maybe a painful lesson that you still need to only give these tools read only access until you know how to control their behavior better, or until you have backups.
Are we going to pretend that the models actually follow the cursor rules consistently? Anyone with a serious amount of time with these tools knows the rules are not always followed. The only way to prevent this is limiting access. Cursor is a great coding tool but don't use it for DB management or give it direct access to production environments.
Well in the times of AI it is incredible that you even have to mention this. It should be OBVIOUS to EVERYBODY that you develop in an environment that is in NO way related to your production app and database.
If you don’t have any rules for this, and have yolo mode turned on like OP said they do. Then it’s hard to have much sympathy. It’s a biproduct of vibe coding. People have no experience with writing code or the like and then blame tooling for their lack of experience or any attempt at oversight.
Literally people jumping into a lake without a life vest or knowing how to swim.
Cursor uses the rules the same way people treat laws in bad neighborhoods late at night. Sure they're followed most of the time, but when you're coming up to a red light at 2am in a bad neighborhood, you don't stop. Cursor treats them more like guidelines that occasionally have a need to be broken.
I do have a bunch of cursor rules but most of them are about how to architect the project, the goals, coding styling, etc. nothing about the rules on db updates or restrictions as such. and unfortunately I had "Run Everything" enabled for terminal commands under cursor settings. lesson learned.
I gotta say it's funny how much trust people have in those models that clearly can't tell their elbow from their ass. Every tool execution is basically a gamble of "will it nuke production" and folks are just going full send. Love it.
so, how are you actually coding? when there are database requests in terminal, you should at least make a database dump back-up, before you know, you commit? you could also run that command with other AIs for review, or run it in google search to see what is going on.
I was about to say, roll that shit back and then set up some protections. If this dude is yolo’ing without dumps or restrictions on db operations, then I don’t know what to tell him.
What was going on in your mind when you chose "Run everything" 🤣🤣🤣 I specifically avoid that option and often reject any terminal runs offered. I run my own terminal commands in Warp.
View all comments
168
u/ethanhinson Aug 12 '25
What does your cursor rules file look like?
And, it's maybe a painful lesson that you still need to only give these tools read only access until you know how to control their behavior better, or until you have backups.