Kiro announced on November 5, 2026, that its persistent development bots were generally available in Kiro Crew. Each bot is set up for a recurring responsibility: it can coordinate worker sessions, keep its own notes and conversation, and bring work back for a developer to review. Kiro’s announcement describes the feature and its setup path.
How to create a Kiro bot
In Kiro Crew, open the bots workspace in the sidebar, add a bot, then choose a default agent or a custom one as its starting point. A custom agent brings its prompt, model, tools, and skills into the setup.
Kiro describes bots as ongoing collaborators rather than one-off prompts. A bot can start several worker sessions in parallel, monitor their progress, redirect work that strays from its plan, and gather results in its continuing chat. If it needs a decision from you, it can ask while continuing tasks that do not depend on your answer.
Begin with a recurring task whose results you can assess, then give the bot only the tools that task needs.
What scheduled work sends back
Kiro’s build-health example schedules a bot to check a continuous-integration (CI) pipeline every 30 minutes. Routine activity goes into a work log; findings or decisions that need attention return to the bot’s chat. Kiro also says that correcting the bot when it investigates an expected failure informs later runs. That describes the intended workflow, not a measured success rate.
A bot can also have its own dashboard, which users can customize. Kiro says each bot has separate memory, tools, and permissions. Users can inspect, edit, or delete what it remembers, and a bot’s requested tools require user approval before they become available.
Memory and permissions stay with each bot
The controls can limit a bot to a defined role. Kiro’s examples include a research bot that can read but not edit files, and a code-review bot that can comment or request changes but cannot approve or merge a pull request. Users can choose a model for the bot and a different one for its worker agents.
That gives developers a concrete starting point: create a bot around a recurring job, set its boundaries, and decide which results should interrupt the ongoing chat.
