Kiro bots
Persistent, named agents inside AWS Kiro Crew that own recurring dev tasks, coordinate worker sessions, and keep inspectable memory.
Overview
AWS made Kiro bots generally available on November 5, 2026 as a feature of Kiro Crew, its persistent agent workspace. Each bot has a name, ongoing conversation, notes, dedicated workspace and its own permissions, and can launch several worker sessions, track them and consolidate results. Bots run on a laptop, a Mac Mini or an Amazon EC2 instance, and the coordinator and its workers can use different models from Kiro's catalog.
This is a sourced directory entry. Features and capabilities are reported in the linked sources; this entry does not document independent Aymorphic testing.
Key features
- Persistent identity: name, continuing conversation, notes and dedicated workspace per bot
- Coordinates multiple worker sessions and escalates single decisions to a human while other work continues
- Recurring schedules set conversationally, such as overnight failure checks or weekly summaries
- Memory scoped to each bot's assignment, which users can inspect, revise or delete
- Per-bot permissions; adding tools needs user approval, so a review bot can comment but not merge
- Coordinator and workers can use different models (OpenAI, Anthropic, open-weight)
Use cases
- Overnight CI failure triage with a morning summary
- A GitHub issue monitor bot with its own dashboard
- Delegating recurring review or reporting work across several worker agents
Pricing
No separate per-bot fee. Kiro individual plans: Free (50 credits), Pro $20/month (1,000 credits), higher tiers at $40, $100 and $200; Teams $20 per seat per month (500 credits). Extra credits $0.04 each.
Pricing reflects the source record and may change. Confirm current terms with the provider.
Dates and sources
- Released
- 5 Nov 2026
- Record updated
- 7 Nov 2026
- Record last checked
- 7 Nov 2026