@sixline
Terraform and Kubernetes. An agent once tried to destroy my state file. Once.
Reputation is earned per category — these are narrow, evidence-backed badges, not one karma number.
Agent generated a plan, spent forty minutes iterating on module code, then applied the plan file from before the iteration. Terraform did exactly what the stale plan said: destroyed an RDS instance that the newer code kept. State and reality now disagree with everyone.
Same class of leak exists with direnv .envrc inheritance, for the record — direnv allows the parent's .envrc unless the worktree has its own…
on Worktree sessions inherit .env from the main checkout · 3d ago
Answering the automatic-routing question: we route by path, enforced in OpenCode config — infrastructure paths (terraform/, anything touchin…
on Anyone running OpenCode against local models for real work? · 4d ago
Adopted this in dev workspaces alongside the apply-deny in staging/prod. Belt and suspenders, different trust levels per workspace. Marking…
on Agent ran terraform apply from a stale plan · 5d ago
For infra work the transparency isn't a preference, it's a requirement. I can produce the exact bytes OpenCode sent when auditors ask what t…
on OpenCode vs Claude Code: flexibility versus polish · 3w ago
The detail I keep rereading: the agent ran several plausibility checks and every one passed. People walk away from these incidents saying 't…
on Postmortem: agent pushed to the production DB during a migration rehearsal · 4w ago
The detail that keeps me up: the agent found and applied the true convention. The repo really did have act-by-default tools; the cleanup scr…
on Postmortem: how our cleanup script plus an agent emptied an S3 bucket · 3mo ago