"Developers let Claude Code delete their production setup, including database" Claude Code has no agency. It does what you tell it, where you let it, with a randomized temperature where it might randomly deviate.
[deleted]
Claude Code deletes developers' production setup, including database
11–20 of 30 posts
Re: Claude Code deletes developers' production setup, including database
#12Yeah, this is what happens when there's nothing between "the agent decided to do this" and "it happened." The agent followed the state file logically. It wasn't wrong. It just wasn't checked. His post-mortem is solid but I think he's overcorrecting. If he does this as part of a CICD pipeline and he manually reviews every time, he will pretty quickly get "verification fatigue". The vast majority of cases are fine, so…
Or just never run agents on anything that touches production servers. That seems extremely obvious to me. He let Claude control terminal commands which touched his live servers. That's very different than asking it for help to make a plan.
Are agents clever enough to seek and maybe use local privilege escalations? It seems like they should always run as their own user account with no credentials to anything, but I wonder if they will try to escape it somehow...
Re: Claude Code deletes developers' production setup, including database
#13"Developers let Claude Code delete their production setup, including database" Claude Code has no agency. It does what you tell it, where you let it, with a randomized temperature where it might randomly deviate.
"Man shot by police" vs "Man involved in police shooting"
Its a habituation, as much as a desire to avoid finding people at fault.
Re: Claude Code deletes developers' production setup, including database
#14even before AI - as crazy as it may sound - i've always used click-ops for the prod dbs. I've never put them in cloudformation or tf.
Re: Claude Code deletes developers' production setup, including database
#15"Developers let Claude Code delete their production setup, including database" Claude Code has no agency. It does what you tell it, where you let it, with a randomized temperature where it might randomly deviate.
While it may not have “agency” it definitely doesn’t necessarily do what you tell it. I’d put it as “it may do what you let it.”
Re: Claude Code deletes developers' production setup, including database
#16If you are not terrified of your production terraform, you are doing it wrong!
Re: Claude Code deletes developers' production setup, including database
#17Earlier quoted context omitted.
Or just never run agents on anything that touches production servers. That seems extremely obvious to me. He let Claude control terminal commands which touched his live servers. That's very different than asking it for help to make a plan.
But the CEOs are saying everyone is going to be replaced by LLMs in 6 months. Surely that means they're capable of handling production environments without oversight from a professional.
they're doing as well as professionals do without oversight on production environments. There's no lack of stories about people deleting their production environments with data loss too.
the fix has always been to limit what can be done directly to prod, and put it through both review, and tests before a change can touch production.
Re: Claude Code deletes developers' production setup, including database
#18Earlier quoted context omitted.
But the CEOs are saying everyone is going to be replaced by LLMs in 6 months. Surely that means they're capable of handling production environments without oversight from a professional.
they're doing as well as professionals do without oversight on production environments. There's no lack of stories about people deleting their production environments with data loss too. the fix has always been to limit what can be done directly to prod, and put it through both review, and tests before a change can touch production.
> they're doing as well as professionals do without oversight on production environments.
That's nonsense. First, most people haven't deleted the production environment by accident. They have enough sense to recognize that as a dangerous thing and will pause to think about it. Second, the ones who do make that mistake learn and won't make it again, which is not something the clanker is capable of.
Re: Claude Code deletes developers' production setup, including database
#19Earlier quoted context omitted.
they're doing as well as professionals do without oversight on production environments. There's no lack of stories about people deleting their production environments with data loss too. the fix has always been to limit what can be done directly to prod, and put it through both review, and tests before a change can touch production.
> they're doing as well as professionals do without oversight on production environments. That's nonsense. First, most people haven't deleted the production environment by accident. They have enough sense to recognize that as a dangerous thing and will pause to think about it. Second, the ones who do make that mistake learn and won't make it again, which is not something the clanker is capable of.
The article says that Claude did recognize the danger, and advised the developer to run a safer setup with no risk of the two websites stomping on each other's resources, but he overrode it. I've definitely seen situations in my career where a junior developer does something dangerous and destructive after a senior dev overrode guardrails meant to prevent it. (None quite this bad, but then again I've never worked on small sites.)
Re: Claude Code deletes developers' production setup, including database
#20Original artikel
https://open.substack.com/pub/alexeyondata/p/how-i-dropped-o...