AWS Kiro, which now styles itself "an agentic development environment," is expanding its remit by launching Kiro Crew bots, described in a Kiro blog post as "a new way to structure and drive agentic work." Each bot is a named, long-running agent with its own memory and sessions, defined and customized for a specific part of a user's work. Kiro is available as a desktop IDE, a command-line interface, a web app, a mobile app, and a personal AI agent (Crew), and it has inherited Amazon Q Developer coding assistant users, who have been directed to migrate to Kiro. An AWS spokesperson said "All of the Kiro bots bill together through a developer's existing Kiro plan," adding that each bot's learned context is intentionally kept separate, while all bots operate within the same Kiro Crew workspace, use the same harness, and have access to the same codebase, project files, MCP, skills, and tools. The article notes potential for duplicated context if many agents process overlapping data without a shared cache, and cites Amazon's concerns about internal token usage and developer complaints about runaway costs in Kiro.