Kiro bots go GA: persistent coding agents in Kiro Crew
AWS made Kiro bots generally available in Kiro Crew on November 5, 2026. A bot is a named, long-running agent with its own memory, ongoing chat, workspace, and schedules for recurring work—not a one-off session.
Why it matters
Per the official kiro.dev post, each bot has a name, avatar, continuing conversation, decision notes, and a dashboard. A bot can launch parallel worker sessions, monitor them, redirect drift, and consolidate results into one chat. If one task needs a human decision, the bot can ask while continuing independent work.
Tools and permissions are scoped per role. A research bot may browse and read files but not edit them; a deployment bot can run scripts and must seek approval before changes. Memories stay separate so release lessons do not bleed into research. Schedules are set in chat—for example overnight CI failure checks or Friday release notes.
Developers open the bots workspace in the Kiro Crew sidebar and pick a default or custom agent (prompt, model, tools, skills). The recommended start is one repeating responsibility that previously forced context juggling across sessions, then adding bots as the process matures.