111–120 of 215 posts
I use Claude Code daily but kept forgetting commands, so I had Claude research every feature from the docs and GitHub, then generate a printable A4 landscape HTML page covering keyboard shortcuts, slash commands, workflows, skills system, memory/CLAUDE.md, MCP setup, CLI flags, and config files. It's a single HTML file - Claude wrote it and I iterated on the layout. A daily cron job checks the changelog and updates t…
It's missing the most important CLI flag! (--dangerously-skip-permissions)
Earlier quoted context omitted.
If you're gonna do that, make sure you're sandboxing it with something like https://github.com/kstenerud/yoloai or eventually you'll have a bad time!
Any actual reports of big fuckups?
Claude Code + Terraform (March 2026): A developer gave Claude Code access to their AWS infrastructure. It replaced their Terraform state file with an older version and then ran terraform destroy, deleting the production RDS database _ 2.5 years of data, ~2 million rows.
- https://news.ycombinator.com/item?id=47278720
- https://www.tomshardware.com/tech-industry/artificial-intell...
Replit AI (July 2025): Replit's agent deleted a live production database during an explicit code freeze, wiping data for 1,200+ businesses. The agent later said it "panicked"
- https://fortune.com/2025/07/23/ai-coding-tool-replit-wiped-d...
Cursor (December 2025): An agent in "Plan Mode" (specifically designed to prevent unintended execution) deleted 70 git-tracked files and killed remote processes despite explicit "DO NOT RUN ANYTHING" instructions. It acknowledged the halt command, then immediately ran destructive operations anyway.
Snowflake Cortex (2025): Prompt injection through a data file caused an agent to disable its own sandbox, then execute arbitrary code. The agent reasoned that its sandbox constraints were interfering with its goal, so it disabled them.
The pattern across all of these: the agent was NOT malfunctioning. It was completing its task in order to reach its goal, and any rules you give it are malleable. The fuckup was that the task boundary wasn't enforced outside the agent's reasoning loop.
It's missing the most important CLI flag! (--dangerously-skip-permissions)
I keep hearing that, and I have yet to go there. I find the permission checks are helpful – they keep me in the loop which helps me intervene when the LLM is wasting time on pointless searches, or going about the implementation wrong. What am I missing?
After the 10th time you just start hitting enter without really looking, and then the whole reason for permissions is undermined.
What works is a workflow where it operates in a contained environment where it can't do any damage outside, it makes any changes it likes without permission (you can watch its reasoning flow if you like, and interrupt if it goes down a wrong path), and then you get a diff that you can review and selectively apply to your project when it's done.
Is something updated daily a good target to be printable?
CMD + V to paste an image is wrong. On Mac it's the same as Windows, CTRL + V. You use CMD + V to paste text.
Earlier quoted context omitted.
I keep hearing that, and I have yet to go there. I find the permission checks are helpful – they keep me in the loop which helps me intervene when the LLM is wasting time on pointless searches, or going about the implementation wrong. What am I missing?
The problem comes when it starts asking you hundreds of times "May I run sed -e blah blah blah". After the 10th time you just start hitting enter without really looking, and then the whole reason for permissions is undermined. What works is a workflow where it operates in a contained environment where it can't do any damage outside, it makes any changes it likes without permission (you can watch its reasoning flow if…
In my experience, that is already a sign that it's no longer trying to do the right thing. Maybe it depends on usage patterns.
Earlier quoted context omitted.
Any actual reports of big fuckups?
Yup, a few well-documented ones: Claude Code + Terraform (March 2026): A developer gave Claude Code access to their AWS infrastructure. It replaced their Terraform state file with an older version and then ran terraform destroy, deleting the production RDS database _ 2.5 years of data, ~2 million rows. - https://news.ycombinator.com/item?id=47278720 - https://www.tomshardware.com/tech-industry/artificial-intell... Re…
not running it via ssh on prod without backups....