Kiro introduces bots so that AI agents no longer have to work in isolation. The new bots act as long-running assistants with their own memory for specific tasks.
Kiro, the AI-powered development environment from AWS, is shifting its focus to managing and directing specialised bots. In Kiro’s definition, a bot is an agent tailored to a specific part of the development process. Each bot has its own memory and its own workspace.
Since its launch in the summer of 2025, AWS has been searching for what exactly Kiro should be. It started out as an AI-powered development environment, but Kiro failed to break through in that niche. Kiro Crew gave it a coordination layer, and the introduction of bots builds on that.
Bots in Kiro
Each bot works from its own chat window, where the user sets the direction. The bot can start and monitor parallel sessions on its own, while collecting the results in a single clear dashboard. When an important decision is needed, the bot asks for input, but it can carry on with the tasks that do not depend on that decision in the meantime.
Security is a key concern here. Each bot only gets the specific tools and permissions it needs for its task. A research bot, for example, can search the internet but has no rights to modify files in the codebase. This also prevents memory from getting mixed up.
Applications in the development process
The new technology makes it possible to automate routine tasks through schedules. For example, a bot can investigate failing builds every night or automatically prepare release notes every Friday.
Kiro gives several examples of what this looks like in practice. A build health bot can check the CI pipeline every 30 minutes and report only the errors that really require attention. Another bot can review pull requests based on earlier decisions on, for example, error handling or specific dependencies.
The bots are available in various environments, ranging from a local laptop to a Mac Mini or an EC2 instance. Users can continuously fine-tune the bots by giving feedback, so the bot gets a better understanding of the desired quality and direction of the work.
Director
With the introduction of Kiro bots, responsibility shifts from carrying out individual actions to keeping the overall course on track. The developer defines what ‘good work’ means and checks the results the bots deliver through their dashboards. This changes the developer’s role from a coordinator of tasks to a director of processes.
The bots are now generally available within the Kiro Crew environment. Users can get started right away by adding a bot and choosing between a standard or a custom agent as the basis.