Skip to content
NO FEED

Understand the changes. Choose the tools. Put AI to work.

← News
News · Wait

Kiro Crew — open-source agent workspace

AWS/Kiro open-sourced Crew: persistent memory, multi-agent orchestration, schedules, approval gates, signed audit logs, Slack/Telegram/Discord surfaces, and reference Apps (Issue Radar, Task Runner, DevFleets).4 It grew inside Amazon as MeshClaw — Kiro says 39,000+ internal builders. Self-hostable without an AWS account. At launch it runs on the proprietary, credit-metered Kiro CLI; Claude Code, Codex and Devin are not day-one harnesses.8

Relevant to: teams already on Kiro who want unattended multi-session work

What the verdict meansAvailable, but early — bugs, limits or price.
Deeper — what is open and what is not
  • Open parts: orchestration layer, Apps SDK, governance via a public steering committee, ACP/MCP-shaped integration surface.
  • Closed part that bites: the agent runtime wired on day one is Kiro CLI.8 Until someone runs a different harness under Crew and shows it working, the open claim stops at the shell around the agent.
  • Existing .kiro steering files, skills and custom agents carry over with no re-setup — that is the adoption path, not a greenfield Claude Code shop.

Sources

  1. kiro.dev — Introducing Kiro Crew · read
  2. infoworld.com — Kiro Crew, Mesaros on Kiro CLI · read
Originally part of the 5 August 2026 edition.

The useful part, in your inbox.

One complete edition every weekday, with practical takeaways.