Kiro
NewAWS-built agentic development environment that turns prompts into requirements, design and task specs, then runs agents in an IDE, CLI, web app or VS Code extension with hooks, steering files and MCP.
Kiro
Explore features, practical uses and pricing below.
Kiro is an agentic development environment built and run by AWS. Its best-known idea is the spec: before an agent writes code, Kiro turns a request into written requirements, a design and a task list, then uses those files to drive and check the work. One shared agent powers a desktop IDE, a CLI, a browser-based agent, a mobile app, a VS Code extension and Kiro Crew, a persistent agent that keeps working while you're away.
How a Kiro spec moves from idea to tasks
The specs documentation describes three files. A feature spec starts with requirements.md, which holds user stories and acceptance criteria. A bugfix spec uses bugfix.md instead and records current, expected and unchanged behavior. design.md covers architecture, data flow, error handling and testing strategy, and tasks.md breaks the work into trackable steps. You can comment on specific passages at each phase before moving on, or use Quick Spec to write all three files in one pass.
When you run every task at once, Kiro builds a dependency graph from tasks.md and groups independent tasks into waves. Waves run in order, and tasks inside a wave run concurrently. That speeds up larger features, but a vague requirements file produces neatly organized work in the wrong direction, so review it carefully.
Steering files, hooks and the rest of the toolkit
- Steering stores project rules as Markdown in .kiro/steering/. The IDE can generate product.md, tech.md and structure.md, and each file can load always, by file pattern, on request or when a request matches its description. Kiro also reads AGENTS.md files.
- Hooks fire on agent events such as a file save, a tool call or the end of a task, and either run a shell command or inject a prompt. Running a linter after every edit is the classic use.
- MCP servers and Powers connect the agent to outside tools; Powers add built-in knowledge that loads on demand.
- Model choice covers models from Anthropic, OpenAI and open-weight providers, or an Auto setting that routes each task.
The IDE download page lists macOS, Windows and Linux builds, and the homepage says Kiro works with Open VSX extensions.
Where Kiro fits, and where it gets in the way
Kiro makes the most sense for teams that already write tickets with acceptance criteria and want the agent held to them. People moving from Amazon Q Developer get a migration guide, which notes that Kiro has no native Visual Studio or Eclipse plugins. If your day is mostly small edits and quick questions, specs can feel like paperwork. Kiro has a vibe mode for quicker requests, but editors such as Cursor are built more around that loop.
A worked example: adding rate limits to an API
- Open the repository in Kiro IDE and generate steering files for the stack and folder layout.
- Create a feature spec: "Limit each API key to 100 requests per minute and return 429 with a Retry-After header."
- Edit requirements.md to add edge cases, such as exempt internal keys.
- Approve design.md once it names where counters live, then generate tasks.md.
- Add a hook that runs the tests after each saved file, run the tasks and review the diff.
Credits, plans and what costs more
The pricing page lists a Free plan with 50 credits a month, Pro at $20 with 1,000 credits, Pro+ at $40, Pro Max at $100 and Power at $200, plus a Teams option with pooled credits and an Enterprise tier through sales. Spec refinement, task execution and hook runs all draw credits, at a rate that depends on the model; the pricing notes say a task costs about 1.3 times as much in Sonnet 4.6 as in Auto. Monthly credits don't roll over.
Questions people ask about Kiro
Is Kiro only for AWS projects?
No. Specs, steering and hooks work on any repository. AWS's role is building and running the service.
Can I keep using VS Code?
Yes. Kiro for VS Code reads the same .kiro folder and uses the same agent as Kiro IDE.
Do hooks cost credits?
Yes. Agent hook execution consumes credits, so a hook that fires on every save adds up.