AWS Kiro aims to solve identity crisis by adding another identity: bot orchestrator
The cloud giant refits its agentic dev tools for agent orchestration
AWS Kiro, the cloud giant's AI-focused integrated development environment, isn't as popular as Microsoft's Visual Studio Code, according to the 2026 Developer Survey by Stack Overflow. However, Kiro has rebranded itself as an "agentic development environment" after previously being an "agentic IDE." It also inherits Amazon Q Developer coding assistant users who have been directed to migrate to Kiro.
Kiro is an AI-powered development environment that helps users build software from prototype to production and is available in various formats, including a desktop IDE, command-line interface, web app, mobile app, and a personal AI agent called Crew. Crew is a persistent, open-source development workspace that acts as agent infrastructure supporting Kiro Web, IDE, and CLI.
To address its identity crisis and make it more appealing, AWS is expanding Kiro's capabilities further. AWS is introducing Kiro Crew bots, similar to other AI agents like OpenAI dots, Grok Bot, Claude Duet, and Meta Muse. These bots are software agents designed to carry out long-running tasks. Unlike isolated sessions, each bot is a named, long-running agent with its own memory and sessions, allowing users to manage multiple agents more efficiently.
Kiro Crew already learns from users' work patterns, but with the introduction of bots, this learning will be more organized.
The concept of named agents with individual tools, permissions, and memories is appealing, as it gives users a sense of having friends to assist them. However, the potential downside is the risk of duplicated context if multiple agents process overlapping data without a shared cache. AWS has addressed concerns about internal token usage and developer complaints about runaway costs by stating that all Kiro bots bill together through a developer's existing Kiro plan.
Each bot maintains its own memory and sessions, ensuring that learned context doesn't interfere with other bots' work. However, all bots operate within the same Kiro Crew workspace, use the same codebase, project files, and tools, so they don't need to independently discover project structures.
Despite the potential benefits, AWS Kiro's growing number of bots could lead to increased token usage. To manage this, AWS suggests using analytics to track bot token consumption. Developers can deploy bots for various tasks, such as reading and labeling trouble tickets, monitoring build health, reviewing code, and confirming release readiness. These bots aim to streamline processes, reduce manual workload, and improve overall development efficiency.
Written by urgent.news from The Register Science's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
