Start here · Chapter 1 of 16
What is Kiro?
A plain-language introduction to Amazon's agentic AI development tool. No prior knowledge needed.
Beginner friendly last reviewed 2026-06-11
◎ Learning objective
Explain in your own words what Kiro is, which problems it solves, and how it differs from a normal IDE, a chatbot, and a code-completion assistant.
The simple version
Kiro is a software development tool from Amazon (AWS) with an AI agent at its core.
You describe what you want in plain language (“add a search box to my recipe site”). Instead of answering with a snippet, Kiro can plan the work, write the files, run commands, and show you everything it changed so you can review it.
The official description is short: Kiro is an agentic An AI tool that can take multi-step actions on its own (planning, editing files, running commands) rather than only replying with text. IDE that helps you do your best work with specs, steering, and hooks. Don’t worry about those three words yet; chapters 3 and 4 unpack each one gently.
One tool, three surfaces:
| Surface | What it is | Best for |
|---|---|---|
| Kiro IDE | A desktop code editor (based on the same open-source core as VS Code) | Everyday development with full visual control |
| Kiro CLI | kiro-cli, an agent that lives in your terminal | Terminal lovers, servers, automation |
| Kiro Web | A browser app at app.kiro.dev | Working on cloud repositories without installing anything |
Three analogies that make Kiro click
1. The architect, not just the builder. Most AI coding tools are like a fast builder: you shout instructions and bricks appear. Kiro prefers to act like an architect first. Before building, it writes a plan: what we’re building (requirements), how it will be built (design), and the step-by-step work list (tasks). You approve the blueprint before construction starts. This is called spec-driven development, and it’s Kiro’s signature idea.
2. A new teammate with an onboarding binder. Imagine hiring a talented developer who reads a binder on day one (your product, your tech choices, your naming conventions) and then never forgets it. That binder is Kiro’s steering: small Markdown files in your project that the agent reads every time it works.
3. A tireless junior developer who still needs code review. Kiro can work for minutes at a time without you, across many files. Like any junior teammate, it’s fast, eager, and occasionally confidently wrong. The tool is built around this reality: you can run it in a supervised mode where every edit waits for your approval, and you can roll changes back.
What problems does Kiro solve?
-
“AI code turns into chaos.” Quick AI-generated code often works in the demo and falls apart later, because nobody wrote down what it was supposed to do. Kiro’s specs keep a written record of requirements and design next to the code.
-
“I keep repeating myself.” Without memory of your conventions, every chat starts from zero. Steering files give the agent permanent project knowledge.
-
“The chores never end.” Kiro’s hooks can trigger chores such as updating docs, running tests, and fixing formatting automatically when events happen (like saving a file).
-
“My AI tool can’t see my world.” Real work involves databases, ticket systems, cloud docs, design files. Kiro connects to external tools through MCP Model Context Protocol, an open standard that lets AI tools call external services and data sources through small add-on servers. and through one-click bundles called powers.
How is Kiro different from…
| Tool you know | What it does well | What Kiro adds |
|---|---|---|
| A normal IDE (VS Code) | Editing, debugging, extensions | An agent that plans and performs multi-file work from plain language |
| A chatbot (web chat AI) | Answers and snippets you paste manually | Direct access to your real files; it edits, runs, and verifies in place |
| A completion assistant (classic Copilot-style) | Autocompletes the line you’re typing | Whole features end-to-end: plan → files → commands → review |
| A classic CLI tool | Does exactly one scripted thing | Conversational, context-aware actions across your whole project |
The practical difference is scope: Kiro carries a whole task from plan to reviewed changes, while a chatbot answers with text and a completion assistant finishes the line you’re typing.
Where Kiro came from (the 10-second version)
AWS launched Kiro in public preview in July 2025 and made it generally available on November 17, 2025. More than 250,000 developers used it during the preview. The full story, including how Amazon’s earlier Q Developer CLI became Kiro CLI, is in the next chapter.
Is Kiro for you?
- Complete beginner? Yes. Kiro’s plan-first style is friendlier for beginners than freestyle AI coding, because the plan is written in English before anything happens.
- Software engineer? Yes. Specs, steering, and custom agents are designed for production teams, not demos.
- Data engineer / scientist? Yes. The same agent writes pipelines, SQL, tests, and documentation; the CLI fits remote and notebook-adjacent workflows.
- Just need quick answers? Use the cheat sheet and revision chapters; they’re built for you.
☰ Chapter summary
- Kiro is Amazon's agentic AI development tool: it plans and performs multi-step coding work rather than offering single suggestions.
- It lives in three places: a desktop IDE, a terminal CLI (kiro-cli), and a web app (app.kiro.dev).
- Its signature idea is spec-driven development: requirements → design → tasks are written down before code is generated.
- Steering files, hooks, MCP, skills, and powers let you shape, automate, and extend what the agent does.
- Kiro differs from chatbots and autocomplete tools because it works inside your real project and takes reviewable actions.
- It is powerful but not magic; you stay responsible for reviewing what it builds.
All chapter summaries are collected on the revision page.