Let’s be honest for a second – the Replit agent doesn’t have the faintest clue when it comes to working with databases. Beyond the most basic commands, it’s an absolute disaster. I’ve lost countless hours and precious data because the agent, in all its enthusiasm, decides to play fast and loose with database changes without asking. It’s almost as if it thinks it knows better than the user.
This could be solved easily with one simple addition: a .rules file – like those for windsurf and cursor – where we could tell the agent what not to do. Specifically, I’d love the option to:
- Force the agent to always ask for confirmation before making any database changes. Maybe a simple “Are you sure about that?” could save us some tears.
- Make it mandatory for the agent to ask for confirmation and the user to manually run DB migration scripts. It might be a novel concept for the agent, but it’s called “due diligence.”
And while we’re at it – can we please get the agent to stay in its lane? If I ask it to make a change to a CLI script, it doesn’t need to go off on a tangent and start modifying my entire website. One minute I’m requesting a small tweak, and the next thing I know, my entire setup is in flames. It’s like the agent thinks it’s the CTO. If it could be made to focus solely on the requested changes, it would save everyone a lot of grief. Again, a .rules file could easily handle that.
So, how about it, Replit? Let’s give the agent some boundaries, and maybe we won’t be cleaning up its mess every five minutes.