· ai-devtools

Why AWS wants developers to stop babysitting their AI agents

AWS first introduced Kiro, its agentic, spec-driven development environment, in July 2025.


It also introduced Kiro Crew in August of this year, its persistent, open-source development workspace that remembers context. Now, to help developers juggle more complex tasks executed in parallel, AWS introduced Kiro bots on Thursday, adding persistent agent memory and delegated workflow management to the toolset. Kiro Crew already carried memory across sessions; bots give each agent its own.

Described as a "named, long-running agent that you define and customize for a specific part of your work" (such as reading new issues in a ticket queue), Kiro bots retain their own memory and start with only the tools provided to them at creation. The bot function also runs its own sessions (by which AWS means parallel worker sessions the bot launches and monitors), so software engineers don't have to track them one by one or weave them together. According to AWS, the arrival of Kiro bots heralds the shift from delegating tasks to delegating processes.

Earlier coverage

Related coverage

Also worth reading

  1. Catching prompt injections hidden in PDFs
  2. How we review 4x more AI code without reading every line
  3. Fireworks says you’re wasting money on AI unless you’re using all the models
  4. How Grab Improved Mobile App Stability by Safely Handling Surge in AI-Generated Code Changes
  5. Open Source pg_vectorsearch Brings More Scalable Vector Search to PostgreSQL