Kiro Crew — open-source agent workspace — from issue No. 002nofeed.dev
No Feed

No feed. One issue a day. Then you are done.

Weekdays — what shipped, what to skip, what it means. Two minutes on a quiet day, four on a heavy one.
Saturday — one argument, made properly. Sunday — nothing at all.

Every claim links to a primary source. Community posts choose what we look at; they never carry a fact on their own. Corrections run above the fold.
Issue No. 002 · 5 August 2026
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

MATTERS TO · teams already on Kiro who want unattended multi-session work
WHAT THE VERDICT MEANS
Available, 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.

Also in this issue

read the whole thing →
Use itClaude Code 2.1.221 → 2.1.222

One issue a day. Three minutes.

Or Saturdays only, if the week is enough. Full issue in the email — no teaser, no click required.

No feed. One issue a day. Full issue in the email — no teaser, no click.