AWS Kiro, 2026: the IDE that asked what you were building
Three requirements ambiguities — that is what Kiro caught in a 2026 comparison that Cursor had not. Each time, Cursor had generated functional code without surfacing the problem; each time, that code required post-implementation rework to fix. The dataset was small, the test narrow, but the finding crystallized something the editor wars had been circling for two years: a tool optimized for asking the right questions before writing any code could outperform a tool optimized purely for writing it.
The IDE was AWS Kiro, Amazon’s replacement for Amazon Q Developer, which launched as generally available on May 7, 2026 — no keynote, no summit, just a product page at kiro.dev. Eight days later, Amazon blocked new Q Developer signups. The company had reached a conclusion that made its previous product obsolete: reactive autocomplete, however sophisticated, shared a structural flaw. It generated plausible code at the moment of prompting, with no record of the reasoning, no agreement on the design, no trail a future engineer could follow. Amazon called the resulting pattern “vibe coding chaos.”
Kiro’s answer was spec-driven development. Describe a feature; Kiro generates three documents before touching a file: a requirements specification in EARS notation (“WHEN the user submits a form THE SYSTEM SHALL validate all fields before sending”), a design document, and an ordered task list. The agent asks clarifying questions. The developer reviews and approves each artifact. Only then does implementation begin, each task scoped small enough to verify independently.
The IDE itself runs on Code OSS — the same open-source foundation as VS Code — so settings, keybindings, and extensions carry over without friction. The new machinery sits in two layers. Steering Files are version-controlled Markdown documents that encode a project’s architectural conventions; they ship with the repository and shape every agent session, ensuring a junior engineer’s AI follows the same rules as a senior’s. Agent Hooks automate the maintenance that typically falls through the cracks: when a React component saves, Kiro reruns the unit tests; when an API handler changes, it regenerates the OpenAPI spec.
The name is a small piece of intentional etymology. Kiro derives from the Japanese きろ, meaning “crossroads” — the point, in Amazon’s framing, where traditional software development meets AI acceleration. By May 2026, that crossroads had grown crowded: Cursor, Zed, ZCode, JetBrains Air, and Google Antigravity were all in the market, each with a claim to the future of coding. Kiro’s claim was structural rather than speed-based.
The timing reflected a genuine shift in what enterprise developers were complaining about. The first generation of AI editors had solved the generation problem. By 2026, the complaints were downstream: code with no documented decisions, no test coverage that matched the actual design, no way to audit what the agent had chosen and why. Full end-of-support for Q Developer’s IDE plugins was set for April 30, 2027 — a hard deadline that pushed AWS enterprise customers toward a tool that required them to decide what they were building before they built it.
For sixty years, code editors had been instruments for expressing decisions already made. Kiro was the first major IDE to treat the making of those decisions as part of its own job.
Sources
- What Is Kiro? AWS’s New AI Coding Platform Explained — Cloudvisor — spec-driven development workflow, Steering Files, Agent Hooks, name etymology (きろ, “crossroads”).
- AWS Kiro Replaces Amazon Q Developer — Enterprise DNA — launch timeline (May 7, 2026 GA, May 15 Q Developer signups blocked, April 2027 end-of-support), feature comparison with Q Developer.
- Amazon Kiro: The Spec-Driven AI IDE Replacing Amazon Q — DEV Community — EARS notation format, AugmentCode comparison showing requirements ambiguities caught by Kiro.