AWS Open Sources Kiro Crew for Asynchronous Coding Agents

Amazon has open-sourced Kiro Crew, a system for running asynchronous coding agents, which was developed internally as MeshClaw and adopted by more than 39,000 developers. The system, now available on GitHub, allows developers to assign tasks such as incident investigation and ticket triage to AI agents that operate without active supervision, with features like shared memory, scheduled jobs, and an OS-level sandbox. Community reaction has been mostly positive, though some users have raised concerns about token consumption costs.

Amazon recently announced Kiro Crew https://kiro.dev/blog/introducing-kiro-crew/ , an open-source system for running multiple Kiro coding agents across sessions, tools, and tasks. The new workspace lets developers assign asynchronous coding tasks to AI agents, allowing work such as incident investigation, ticket triage, migrations, and PR monitoring to continue without active supervision. Kiro Crew supports persistent, multi-session development work through shared memory, reusable skills, scheduled jobs, concurrent agents, and purpose-built Apps. Agents can retain project context, run tasks while developers are away, delegate work to subagents, and integrate with external tools through MCP and webhooks. Developed internally at Amazon as MeshClaw and reportedly adopted internally by more than 39000 developers, Kiro Crew is now available as an open source project and can run locally or on infrastructure developers control. Bolin Chen https://github.com/bolichen97 , senior software engineer at Amazon, Zejiang Joe Guo https://github.com/iamwhatever , principal SDE at AWS, and Zezhen Xu https://github.com/CrysisDeu , senior software engineer at Amazon, write: Three of us wanted something simple that wasn’t available internally, a way to kick off a task, walk away, come back to something worth reviewing, and to run several tasks at once instead of babysitting one prompt at a time. We were inspired by the momentum of OpenClaw and various tools with self-learning agents taking over AI work, but we needed something that met our security requirements for internal development work. Kiro Crew orchestrates agents through the Agent Client Protocol http://github.com/zed-industries/agent-client-protocol ACP , providing live visibility into their work. The Activity view shows each agent’s plan, tool calls, approval gates, and results as they happen. Chen, Guo, and Xu add: Kiro Crew ships with defense in depth from day one, an OS-level sandbox, denied-by-default commands, suspicious-pattern blocking, input validation, sensitive-path blocking, credential redaction, and a signed audit log of every action. Plenty of agents are open source. Kiro Crew can be customized to fit existing tools and workflows through MCP, Apps, orchestration, and reusable skills. It also supports skills built for other open, standards-based agent platforms without modification. Kiro Crew's Activity view. Source: Kiro blog. The community reaction has been mostly positive https://www.reddit.com/r/kiroIDE/comments/1vfhqy9/introducing kiro crew an open source/ , with several practitioners highlighting the reported internal adoption. Muhammad Ishaq, CTO at Nextbridge, comments https://www.linkedin.com/feed/update/urn:li:ugcPost:7490492322997235712/?dashCommentUrn=urn%3Ali%3Afsd comment%3A%287490645309421842433%2Curn%3Ali%3AugcPost%3A7490492322997235712%29 : The internal adoption numbers say more than the feature list honestly, 39,000 builders and 500 contributors in six months without a mandate means people were actually solving real problems with it, not just trying a new tool because it existed. that kind of organic growth inside a company this size is rare and usually means the tool earned its place before marketing got involved. While many developers are experimenting with CI/CD migrations, Dependabot triage, scheduled tasks, and long-running work https://www.reddit.com/r/kiroIDE/comments/1viu5yd/what have you built with kirocrew/ , some have raised concerns about costs https://www.reddit.com/r/kiroIDE/comments/1viu5yd/comment/p2h8s44/?utm source=share&utm medium=web3x&utm name=web3xcss&utm term=1&utm content=share button , reporting that Crew can consume tokens significantly faster than Kiro CLI. Mathi M, senior solution architect at Verizon, comments https://www.linkedin.com/feed/update/urn:li:activity:7490462121064046592/?dashCommentUrn=urn%3Ali%3Afsd comment%3A%287490544543948312576%2Curn%3Ali%3Aactivity%3A7490462121064046592%29 : Having background subagents handle parallel jobs without blocking the main workflow is exact target engineering builders need. Stacking context across sessions instead of starting from scratch will save tons of redundant prompt engineering. Kiro Crew runs on the Kiro CLI https://kiro.dev/cli/ and can use existing , including steering files, skills, and custom agents. It is released under the Apache 2.0 license and is available for macOS, Linux, and Windows, with integrations for Slack, Telegram, and WeCom. .kiro configurations https://kiro.dev/docs/configuration/ According to the announcement, the project expects community participation in development and roadmap planning, with Kiro and AWS engineers initially maintaining the project and external maintainers able to join as contributors emerge.