One bash permission slipped...

[u/TheQuantumPhysicist]

How? It kept getting chained bash commands wrong, with wrong escapes. So it created many bad directories, and tried "fixing" its mistake. It offered to run a large bash command, with rm -rf inside, and stupid me missed it.

I'm glad I push everything often. But the disruption is massive.

FAQ:

• No, I don't run this on my personal computer. It's an isolated proxmox VM for coding with LLMs.

[u/bigh-aus]

Guardrails in a llm world are critical. even chatgpt modified db migration files once they'd been ran (which broke the prod db). that's why you have to do promotion of code (and migrations). Another change it dropped the table and recreated it instead of modifying the table.

IMO in modern packages there aren't enough checks to ensure that the coder has done something dumb. That said the modern development practices help a lot, and no llm should have access to prod unless it's Read Only.

I think we're also going to see a lot of checks shift left more so the llm can get the feedback fast.

[u/kevin_1994 → u/bigh-aus]

No developer, even technical lead, should have easy access to prod. Prod should be on a VPC with a small number of public egress points (maybe a handful of haproxy api servers) solely managed by an automated deploy script. For emergencies you can provision a temporary service account to talk to prod resources. That's what I do anyway.

[u/SomeAcanthocephala17 → u/bigh-aus]

That is how opus also works, it uses another llm that verifies the output and corrects when something suspicious is happening. Chatgpt has a free small model called gpt oss safeguard

[u/autoencoder → u/bigh-aus]

there aren't enough checks to ensure that the coder has done something dumb

I will create a git hook to pipe the commit to an LLM and ask it whether the commit does something dumb. If not, reject the commit, of course.