Why it matters
A review of nine coding-agent incidents from 2025 and 2026 separates shell, path, and harness failures from constraint decay and excessive permissions, then maps them to concrete controls for identities, filesystems, approvals, verification, logging, and backups.
My takeaway: The recurring failure is ordinary operator error executed at machine speed without enforced boundaries. Protect production below the prompt layer with scoped agent identities, sandboxed filesystems, out-of-band approval for destructive actions, read-after-write checks, command logs, and tested off-host backups.