Kiro

What Is Kiro?

Kiro is AWS's agentic AI development environment — a VS Code-compatible IDE designed around the premise that AI agents need more structure than a chat prompt to build production software . It launched in preview in mid-2025, reached general availability on November 17, 2025 (adding a Kiro CLI for the terminal alongside the IDE), and has iterated rapidly through 2026 with custom subagents, agent skills, and enterprise controls .

As of June 2026, Kiro is also AWS's designated successor to Amazon Q Developer: AWS closed new Q Developer signups on May 15, 2026 and will end support for Q Developer IDE plugins and paid subscriptions on April 30, 2027, funneling that user base toward Kiro .

The core philosophy: agents work better with structured input. Rather than "vibe coding" from a prompt, Kiro converts natural language into specs, designs, and task lists before any code is written.

How It Works

Three-Layer Agent System

Specs — Kiro's signature feature. You describe what you want; Kiro generates structured requirements, a design document, and implementation tasks. Each phase has a human approval gate. This is philosophically aligned with GitHub Spec Kit's approach but built directly into the IDE.

Hooks — Background automation triggers. When you commit, save, or complete a task, hooks can automatically run agents for documentation updates, unit test generation, or performance optimization. Think CI/CD but for agent workflows inside the IDE.

Skills — Based on the Agent Skills open standard (SKILL.md format) . Skills are modular instruction packages loaded on-demand when the agent identifies a relevant task. Kiro supports two discovery tiers:

• Workspace skills (.kiro/skills/) — committed to version control, shared with the team, scoped to that project
• Global skills (~/.kiro/skills/) — personal, available across all workspaces

Workspace skills take precedence when names collide . Skills can be imported directly from GitHub URLs .

Powers — Kiro's proprietary enhancement layer. Curated packages of MCP servers, steering files, and hooks that can be dynamically loaded. Powers go beyond skills by bundling tooling configuration alongside instructions.

Custom Subagents

Added in Kiro 0.9 , custom subagents let you split context by domain. A frontend-agent loads Chrome DevTools and component libraries. A backend-agent loads database servers and API docs. Each manages its own context window instead of one agent loading everything.

Kiro CLI

Announced at GA, the Kiro CLI brings the Auto agent, Claude Sonnet 4.5, and Claude Haiku 4.5 to the terminal, with steering files and MCP tools carried over from the IDE . GA also added property-based testing for spec correctness, checkpointing to rewind agent changes, and multi-root workspace support .

Model Selection

The default "Auto" agent uses a mix of frontier models (Sonnet 4.5 plus specialized models) with intent detection and caching for cost optimization. Paid plans can also select Claude Sonnet or Opus variants directly, with credit consumption varying by model .

Pricing

First-time upgrades to any paid plan get a $20 subscription credit. Unused monthly credits do not roll over . Kiro is also available in AWS GovCloud (US) regions at roughly 20% higher pricing, with no free tier .

Team plans mirror individual pricing and add centralized billing, usage analytics, SAML/SCIM SSO via AWS IAM Identity Center, organizational dashboards, and extension registry governance . Qualifying startups (up to Series B) can get one year of Pro+ free .

Strengths

• Spec-driven development is genuinely novel — forcing structured planning before code generation addresses a real problem with agent-generated code quality
• Three-layer system is well-designed — specs for planning, hooks for automation, skills for expertise hits different needs without overlap
• AWS backing — enterprise credibility, IAM integration, and long-term viability
• Open standards adoption — uses agentskills.io SKILL.md format rather than proprietary skill system
• Autonomous agent mode — can run large tasks independently without step-by-step prompting

Cautions

• Reliability complaints — Reddit feedback includes reports of bugs, agents editing internal snapshots instead of actual files, and inconsistent behavior
• IDE maturity — as a newer VS Code fork, it lacks the extension ecosystem maturity and polish of Cursor or standard VS Code
• Credit system opacity — complex prompts consume multiple credits unpredictably; hooks consume at least 1 credit each. AWS previously had to acknowledge a billing bug that drained developers' limits faster than expected
• Claude dependency — most criticism traces back to underlying model limitations rather than Kiro's tooling, but users experience it as Kiro's problem
• Forced migration friction — Amazon Q Developer users must move by April 2027, and Kiro's credit model differs significantly from Q Developer's request-based pricing

What Developers Say

No directly attributable verbatim developer quotes could be verified for this update — the most active feedback channel, r/kiroIDE , blocks automated retrieval, and press coverage of the Q Developer transition paraphrases community sentiment without naming sources . The recurring themes in that coverage and in Reddit threads: the spec workflow genuinely catches design mistakes before code is written, but the credit system's unpredictability and the requirement to adopt Kiro's own IDE rather than existing VS Code installs remain the loudest complaints as of June 2026.

Competitive Positioning

Kiro's differentiator is the spec-driven workflow + hooks combination. No other IDE enforces structured planning before implementation. The tradeoff is maturity — Cursor has years of polish that Kiro is still catching up to.

The Tembo Angle

Kiro's spec-driven approach validates what orchestration platforms like Tembo have been building toward: agents need structured context and planning phases, not just prompts. Kiro does this within a single IDE; Tembo does it across fleets of agents. The hooks system is particularly interesting — it's essentially lightweight orchestration triggers built into the development loop.

Bottom Line

Recommended for: Teams that want structured AI development with planning phases, especially those already in the AWS ecosystem. The spec-driven workflow genuinely reduces the "agent wrote the wrong thing" problem.

Not recommended for: Developers who want a polished, stable daily driver — Cursor is more mature. Solo developers who prefer speed over structure may find specs overhead.

Outlook: Kiro has the right ideas (specs, hooks, skills, subagents) and the right backing (AWS). With Amazon Q Developer retiring in April 2027, AWS has consolidated its coding-agent bet entirely on Kiro — which guarantees investment but also raises the stakes on fixing the reliability and credit-transparency issues. If they do, the spec-driven approach could become the standard for production-grade agentic development.