alt Hacker NewsAt the very least you should give it a non-prod copy of the database, not direct access to the DB actively powering production right now.
I've done work for a hedge fund where the DB ran directly on the manager's desktop. I worked with my local copy and sent an update script, and he had a second copy he ran on to verify.
Even with humans you shouldn't be working directly against the prod DB in these cases!
Replies
2ndorderthought • yesterday at 10:51 PM
There is literally no excuse. The fact that there is any resistance to this let alone from multiple people terrifies me.
➕ show 1 reply
Yes, I just think there's a sane way to do things that is not "never let LLM agents do things".
For dev/prod staging though, there's that other story on HN right now of an LLM agent that maneuvered it's way to prod credentials and destroyed prod. And backups went along with it. I'm paranoid enough to think backups in this use case means out-of-band uncorrelated storage.