{
  "id": 18740492,
  "title": "Why AWS wants developers to stop babysitting their AI agents",
  "url": "https://urgent.news/2026/11/07/why-aws-wants-developers-to-stop-babysitting-their-ai-agents",
  "topic": "ai",
  "section": "AI",
  "published": "2026-11-07T15:30:00.000Z",
  "source": {
    "name": "The New Stack",
    "slug": "the-new-stack",
    "url": "https://thenewstack.io/kiro-bots-agent-memory/"
  },
  "original_language": "en",
  "account": "AWS has unveiled Kiro bots, its latest offering aimed at developers, designed to streamline complex tasks executed concurrently. These bots offer persistent memory and delegated workflow management, setting them apart from previous versions. Unlike Kiro Crew, which carries memory across sessions, each bot retains its own memory and begins with predefined tools. The introduction of Kiro bots marks a shift from delegating tasks to delegating processes, according to AWS. This development is led by Kathy Kam, AWS's agentic AI director, who explains that developers often end up as intermediaries, tracking sessions and ensuring continuity. With Kiro bots, developers can focus on defining what needs to be built rather than managing sessions.\n\nEach Kiro bot operates with a defined set of tools and permissions tailored to its specific role, such as research, deployment, or issue tracking. This ensures that mistakes are less likely to resurface and that each bot remains focused on its designated responsibility. Trust in these bots is built through their track record, as they are only granted access to the tools necessary for their assigned tasks. For instance, a research bot can search the web and read files but cannot modify them, while a deployment bot has the authority to run deployment scripts and request approvals before executing changes. Developers retain control over what each bot can access, allowing for a clear hierarchy of responsibilities based on the bot's authority rather than its intelligence.\n\nKiro bots are designed to communicate through chat channels, where developers can provide direction and monitor ongoing sessions. They can also ask developers for additional tools or approvals, ensuring that automated processes do not override human judgment. Developers can set routines for bots, such as investigating build failures overnight, allowing them to operate independently while still being guided by human oversight when necessary. AWS emphasizes that while bots can accumulate extensive knowledge across a team, they do not operate independently of human accountability. Each bot is assigned specific roles, such as issue intake or release readiness, ensuring that the software engineer maintains ultimate control over the development process.",
  "summary": "AWS first introduced Kiro, its agentic, spec-driven development environment, in July 2025. It also introduced Kiro Crew in August of The post Why AWS wants developers to stop babysitting their AI agents appeared first on The New Stack .",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}