AWS Open-Sources Kiro Crew, Its Coding-Agent Orchestrator

AWS open-sourced Kiro Crew on August 4, per SiliconANGLE, corroborated by InfoWorld. The persistent workspace runs coding agents across repositories and sessions instead of living inside one chat.

Adoption already happened before the release. AWS says 39,000 Amazon builders used Kiro Crew internally in under six months, with nearly 500 contributors shipping 597 updates at 143 commits a week.

The release is Apache-2.0 licensed and runs locally or on a machine you manage. It ships persistent memory, cron and webhook scheduling, approval workflows, sandboxing, and signed audit logs, plus a web and desktop dashboard for watching agents work.

Here's the choice that matters: AWS open-sourced the scheduler, the approval workflow, and the audit trail under Apache-2.0, but kept the coding agent proprietary. That's a bet that lock-in lives in who controls approval and audit, not which model writes the code. Aurora Mobile made the opposite call with LoopAgent, arguing in-house execution engines beat open-source orchestration. AWS is betting the market disagrees, at least at the layer that touches production repos while nobody's watching.

Sandboxing and signed audit logs matter more once agents run unattended overnight. A separate policy shift shows the same tension: Rust adopted a policy banning autonomous agents from contributing code outright, fine to review, not to create. That's the exact governance gap Kiro Crew's approval workflows are built to answer. Whether a signed audit log satisfies a team with a policy that strict is a separate question the release doesn't answer.