AWS's Kiro Crew Keeps Coding Agents Running Around the Clock, With a Heartbeat Monitor to Catch Them When They Stall

AWS announced Kiro Crew on August 4, 2026, an "always-on" workspace that runs Kiro coding agents and their sub-agents completely unattended, around the clock rather than only during an active chat session. The product includes persistent memory that carries across sessions, scheduled recurring jobs so an agent can run the same task on a cadence without a human kicking it off each time, and a heartbeat-monitor system that watches for stalls or failures and escalates to a human when something actually needs attention.

Control happens through chat, and AWS built in support for multiple interfaces at once, including Slack, Telegram, Discord, and WeCom, so a team can check in on or redirect a running agent from whichever tool it already lives in day to day.

AWS is also claiming interoperability with third-party agent orchestrators, naming OpenClaw and Hermes specifically as systems Kiro Crew can work alongside rather than compete with directly. That is a notable choice for a cloud vendor: rather than trying to be the only orchestration layer a team uses, AWS is positioning Kiro Crew as infrastructure other orchestration tools can plug into, which lowers the switching cost for a team that already has an agent workflow built around something else.

The heartbeat-monitor piece is the part worth paying attention to if unattended agents make you nervous, and they should. An agent running continuously without a human watching is only as safe as its failure detection, and a system built specifically to escalate to a person when something stalls is a meaningfully different design than one that just keeps retrying silently until someone notices the output is wrong.