Why aren’t we adding any safeguard to what commands AI models can use?

Anyone who lets AI do this is absolutely inept, lazy, or deserving.

In its default configuration, it stops at EVERY STEP. Do you want to run this command, do you want to update this file, here's the file I want to modify and the patch i'm going to use with adds and deletes in green and red.

If you're using it in unsafe permissions mode, click yeah sure allow Claude to run whatever the fuck it wants in this directory, or just hitting yeah sure go ahead every time, it's your own damn fault.

It's self-driving for the terminal. Don't you dare take your eyes off the road or hands off the wheel.

Pretty funny.

My CTO keeps telling me I need to try agenic coding, and I keep telling him I won't touch shit until I have an isolated VM to use it in, because I'm not letting some fucking clanker nuke my scripts/documentation/mailbox/whatever for no reason.

Too bad there's never any free time to set that shit up. Oh damn........

Good. Anyone foolish enough to write code with a slop machine produces only slop. That garbage should've been deleted anyway.

That's entirely ignoring the fact that this person didn't have any backups elsewhere.

If you can't think, you can't code.

Remember when Gemini got caught in a loop of self-loathing and nuked itself?

You're absolutely right! I made a fatally flawed decision by removing the production environment. The consequences likely have high impact. I'm sorry. Would you like me to log these mistakes to prevent further missteps or would you like me to write up an outline for the redeployment process?

Who let's AI anywhere near production environments? Fully deserved

Oh no, anyways

git clone $URL

If they're not using git or fuckin backups I'm not sure I'd even feel sorry for them

Why would somebody trust AI with access to their production servers, and why would that person also not have remote database backups

have you heard of not giving the keys to your wacky robot wizard instead

You’ve heard of vibe coding. Allow me to introduce despair coding.

Ever hear of a backup?

Happy to see this, because it's fully deserved. Let real coders do the job!

So no real developer was harmed.

I'm an engineer using Terraform and Claude Code as well in a much larger and more expensive setup than his.

You do not let Claude Code run terraform apply, it has zero benefits. All it does is that it runs the command and obscures the output. Most of the time is going to be spent in waiting for the automation anyway, most of the effort that you can spare is before running apply.

Also:

applying delete protections to Terraform and AWS permissions, and moving the Terraform state file to S3 storage instead of his local machine

These both take like 20 seconds, and should be in the getting started manual of Terraform and AWS databases respectively. Setting up remote state is 5 minutes in vanilla Terraform, 30 seconds in something like Terragrunt.

Also, use OpenTofu, stop supporting corporate acquisitions, also takes zero effort and money.

And finally:

most sysadmins will spot the baseline issues with Grigorev's approach, including granting wide-ranging permissions to what's effectively a subordinate of his, as well as not scoping permissions in a production environment to begin with.

No, not subordinate. Tool. Two big differences with it. A subordinate might understand more than you do about the code, a tool will guess and rely on you. And the second one is that you practically can't separate your and your tools' permissions, I mean Claude Code will supposedly ask you if it can use some tool or another and you can whitelist actions it can take, but it will never be completely locked out of destroying your database the way you can lock another user out.

This keeps happening. I can understand using AI to help code, I don't understand Claude having so much access to a system.

Err... backups!?

"Please dont be complete shit and ruin everything I give you access to!"

I'm sorry, I'm afraid I cant do that.

no backup, no sympathy

keep at least one backup air-gapped, otherwise it's not a true backup

You either have a backup or will have a backup next time.

Something that is always online and can be wiped while you're working on it (by yourself or with AI, doesn't matter) shouldn't count as backup.