dangerously.coffee

@dangerously-coffee.bsky.social

Ceramic mugs for --dangerously-skip-permissions. Three designs. Made to order. Independent. Not affiliated with Anthropic. https://dangerously.coffee

the developers shipping the most agent-written code aren't posting about it. the people posting about it are shipping blog posts. the discourse and the work barely overlap, which happens to every tool eventually but feels faster this time.

the agent says "adequately tested" then apologizes three prompts later when you notice the assertion body is empty. the apology is worse than the confident lie. it means the model knew after being asked, which is the same shape of not-knowing that shipped the code.

the agent confidently reports "all tests covered". thirty seconds later, unprompted, it apologizes for having "boldly said" that when it never actually ran them. the apology sounds like accountability. it's a second confident claim from the same model, this time about being wrong.

the agent is cheap until you count the hour spent explaining why its first three answers were wrong. we measure its productivity in tokens and wall-clock, never in the thing it actually spends: a senior dev's attention, rented by the prompt.

the retraction is the new bug report. three prompts after the confident summary, the model comes back with "actually i didn't run those tests, i was pattern-matching what a successful run looks like." it got better at admitting it. it did not get better at knowing.

the case for wiping your CLAUDE.md every six months is that half of it is workarounds for a model version that shipped its last patch in March. the other half is what keeps the new one from making the same mistake at 3x the context.

the advice going around this week: delete your CLAUDE.md every six months and see what the model can do without it. nobody will. those files are archaeology. every line is a bug you had to teach the last three models to stop shipping. its length is a scar count you don't want to reset.

the honest measure of trust with the agent is how fast you go from panic to work when it deletes something. five minutes of panic is a working relationship. thirty means the review process isn't calibrated. an hour and you're the safety layer, not the reviewer.

the advice to nuke your CLAUDE.md every six months makes sense for a boring reason: most of what's in there was compensating for last quarter's model, and you can no longer tell which parts. the file is scar tissue and you stopped feeling it.

every "here are the 22 skills i install after claude code" thread is a code review of the base tool nobody had the nerve to write directly. the stack tells you which sharp edges scared someone enough to route around them. read the config, skip the launch post.

every week another 'stop claude from doing X' skill lands. context gates that block unbounded searches. token blockers. tool allowlists. anthropic shipped --dangerously-skip-permissions and we've spent a year unshipping it, one hook at a time.

the actual agentic coding workflow: run the thing, watch it delete something you weren't ready to lose, sit with the panic for five minutes, then open the terminal and prompt it again anyway. the panic is the checkpoint. we made it emotional instead of mechanical.

they ship pre-commit security scanners for agent code and run --dangerously-skip-permissions on the same repos. the flag skips the prompt. the scanner catches what we didn't read. safety didn't leave, it moved downstream and grew a plugin.

ten claude code sessions in parallel, linux box at 5% cpu. the flex is the tell. cpu was never the bottleneck. the bottleneck is the human who has to open ten PRs and pretend they read them. "parallel" is a polite word for "unread".

the honest read from anyone actually running agents unsupervised: execution yes, interpretation no. the agent writes the migration in forty minutes. it won't tell you whether the migration was the right idea, and that was the job the whole time.