Human developers should not develop with the production DB, why the hell would you give an AI the rights to touch the prod DB?
You don’t test in production?
Everyone has a test environment, some are lucky to have a separate production environment.
Yolo bich
Dangerously-skip-permission is carte blanche for the model to do whatever it pleases with your system. If you happen to have access to a production database on your system, then the model also has access to it, should you use that option.
that assumes
- the user does have access to a production db;
- the agent has access to a terminal from which they can reach the production machine (not in a container, different network, or similar);
- access does not require interaction (like entering password);
- the agent deliberately decides to access a production database to solve a development problem, and that was not the user requesting it;
- the agent manages to find the database credentials in production;
- the agent is left unattended.
Possible? Sure. It’s also possible that I drink half a bottle of vodka on a Friday night and mess up with production.
Naturally.
You should still probably not use dangerously-skip-permissions, though.
Yes, but the question is why the hell do you have access to a production database in the first place?!
And if so, how is it on the same machine you can run Claude code on?!
I’ve worked at places where senior devs have access to prod for emergency fixes but usually the procedure is to use a VPN AND an ssh key with a passphrase. Usually.
Startups and small companies where there simply aren’t enough resources to set up proper operational controls
No no no I’m not running Dev ops on the production system. I’m running prod ops on the developer system.
I’ve worked at several places where I’ve been able to access production databases.
No need to be so dramatic about it, really.
Or maybe just don’t play Russian roulette with your code?
C-suite response:
(Edit: or maybe I messed this up - I guess it should be “yes” in this case? 🤔)
Just because things can be done quickly does not mean they should be.
Something like
--dry-runthere?does dry running have any meaning on a function that is inherently stochastic?
Are you sure you don’t need the lube?
I am using on Mac and I have few hooks, one is replace any rm to trash command. You can make hooks for the most dangerous patterns and use dangerous-skip-permissions with a bit more safety.
I truly hope that there is nothing irreplaceable on that machine, bc you might be about to FAAFO.
I think you’re only supposed to use the dangerous skip thing when it’s running inside a docker container
Where the hell are they? That’s not a roller-coaster.
It’s probably just a themed train, there’s why it looks like not a roller coaster
Expedition Everest at animal kingdom.
https://knowyourmeme.com/memes/roller-coaster-dad
Expedition Everest coaster at Disney’s Animal Kingdom.
It looks like a rollercoaster to me. Maybe one of those digital rollercoasters, where you get a “4d” experience, but actually the chairs just shake about a bit. But could as well be a regular (simple) rollercoaster, they do have that bar across their laps.
digital rollercoasters
Excuse me, what!? So you pay expensive fares and stand in line for hours to experience the same thing you can at home with an office chair with a leg missing in front of a TV???
Nah, there’s never a line for those rides.
