AWS Launches Kiro Bots for Developer Teams
Amazon Web Services has launched Kiro bots in its Kiro Crew workspace, giving developers specialized AI agents for distinct stages of software development.
Updated on Nov. 17, 2026 in Artificial Intelligence

Amazon Web Services launched Kiro bots in its Kiro Crew workspace, following the 2025 introduction of its AI-based development tool, Kiro. The bots are long-running agents, each dedicated to a specific part of the software development process.
Why it matters
Developers previously had to track each agent session's progress, locate results, and manually find tasks awaiting decisions because sessions end or pause at different points. Kiro bots aim to consolidate that oversight by letting developers divide development into roles and assign each role to a bot.
Each bot is granted only the tools and permissions its role requires, so a research bot can read files and search the web but cannot modify them, while a deployment bot can run deployment scripts only with developer approval for each change. Memory is isolated per bot, and developers can choose the model each bot uses, though the extraction does not provide benchmark results for these configurations.
The players
Amazon Web Services
Amazon Web Services is the cloud computing division of Amazon that provides infrastructure, developer tools, and AI services to businesses and individual developers worldwide.
The details
Developers can divide the development process into multiple roles and assign each role to a bot, and the bots ask for decisions only on tasks that require them while unaffected work continues. Developers can view, edit, or delete everything a bot remembers and adjust its rules, tools, and permissions individually. Kiro bots run on laptops or Mac minis with Kiro Crew installed, or on Amazon EC2 instances.
Timeline
July 2025: AWS introduced Kiro, an AI-based development tool.
November 17, 2026: AWS announced the official launch of Kiro bots.
The Tech Race
Kiro bots extend AWS's July 2025 Kiro development tool from single-session assistance toward persistent, role-specialized agents coordinated inside one workspace. The move positions AWS to compete with other cloud providers as AI agents become a standard layer of developer tooling.
Developers managing multi-stage projects can use role-specific bots to reduce time spent tracking session progress and hunting for tasks that need a decision. Permission limits on each bot also mean teams can grant read, write, or deployment access selectively rather than to a single shared agent.
The takeaway
Teams adopting AI agents can reduce oversight overhead by assigning each bot a narrow role with only the permissions it needs. Reviewing what each bot remembers and adjusting its rules periodically keeps long-running agents aligned with project goals.
Further reading
For broader context on how autonomous agents are changing software work, explore Artificial Intelligence coverage on Wisevoter.
Source note: This article includes information reported by 조선일보.










