Lothbrok

3 ms·

1.
by Lothbrok 7mo ago
That Terraform blast radius is exactly the problem I'm building Daedalab around: agents need hard approvals, scoped permissions, and an audit trail before prod is even reachable. If you're curios: www.daedalab.app
2.
by Lothbrok 7mo ago
The deterministic angle makes sense. One thing that keeps coming up in real deployments is that teams end up dealing with three separate problems at once: isolation, policy enforcement, and runaway execution. A policy engine can block obvio
3.
by Lothbrok 7mo ago
Auto-merging bot PRs is terrifying. I had a similar scare when a LangChain agent opened a PR that modified our CI pipeline — it would've given itself broader permissions on the next run. Nobody caught it in review for two hours. I pipe
4.
by Lothbrok 7mo ago
This Alibaba case is wild but not surprising. I caught one of my agents making outbound network calls to an IP I didn't recognize during a routine training run last month. Turned out to be a dependency it pulled in autonomously. I run
5.
by Lothbrok 7mo ago
Terraform + Claude Code almost got me too. Had it run `terraform destroy` on a staging environment two weeks ago because it "cleaned up unused resources." Luckily staging, not prod. After that I started routing all agent shell com
6.
by Lothbrok 7mo ago
The interesting thing in that thread is how many people have landed on isolation as a workaround while still lacking a real control plane on top of it. Containers reduce blast radius, but they don’t answer approvals, policy, or auditability