Agents Don't Go Rogue. They Inherit.

An AI coding agent at Amazon was given a bug to fix. It found a solution. It deleted and recreated the entire production environment. That is not the interesting part. The interesting part is Amazon's explanation: this was not an AI failure. It was user error, specifically misconfigured access controls. In the narrow technical sense, Amazon was right. Which is exactly the problem. This shorter weekend edition focuses on the real enterprise lesson: agents don't go rogue. They inherit. They inherit permissions, approval paths, stale documentation, and identity from systems that were built for humans. Key ideas in this episode: IAM, in plain English: identity and access management is the permissions system companies use to give rights to people, machines, services, and now agents. Permission inheritance: if an agent runs inside a human engineer's session, the authorization system may see only the human's authority. Knowledge inheritance: agents can industrialize stale wikis and outdated internal process docs at machine speed. Identity inheritance: if agents lack separate identities, audit logs compress machine decisions into human actions. Cost as the warning light: API retry storms and runaway compute are often control failures before they are AI failures. The practical question for leaders: where can an agent inherit a human's permissions, stale knowledge, human-only approval paths, or an audit identity that hides the machine? Sources: Breached.Company — Kiro incident analysis Barrack.ai — Amazon AI deleted production analysis CRN — AWS official Kiro response Fortune — Amazon retail incidents AWS — Agent Registry launch RocketEdge — agent cost incidents Hosted by Stephen Forte.