Introducing Kiro for VS Code
David Jutrsa
Product
Johnny Sooter
Engineering
Jonathan Breedlove
Engineering
Today, we’re launching Kiro for VS Code, generally available on macOS, Windows, and Linux. Install it from the VS Code Marketplace or Open VSX, sign in, and build with the Kiro agent without leaving the editor you already use. It works with every Kiro plan, with no change to your plan or billing.
Your editor holds years of small decisions, like keybindings, themes, settings, and the extensions your team depends on. For many teams, Visual Studio Code (VS Code) is the standard, and switching editors to try a new agent isn’t an option. Kiro already works in VS Code, JetBrains IDEs, Zed, Neovim, and other editors through the Agent Client Protocol. Now, Kiro comes to you as a native extension, with approve for me, specs, steering, MCP, workflows, and memory built in.
If your team already uses Kiro IDE, Kiro for VS Code reads the same .kiro folder. Your specs, steering files, skills, hooks, powers, and MCP servers work without changes. Specs move both ways. A spec started in Kiro IDE opens in VS Code with its task buttons, and one created in VS Code opens in Kiro IDE unchanged. Each teammate can pick an editor, and the project setup stays shared.
When Kiro answers, it shows which steering files it included. Click one to open the source file, see why Kiro made a choice, and adjust the rule if you need to.
Kiro has its own hub in the VS Code side bar. Start a vibe session to ask a question or make a quick change, or start a spec session when the work needs a plan first. Responses and tool activity stream in as Kiro works. You can stop a turn at any time, and your sessions are still there after you reload the window.
Give Kiro the context it needs with #: a file, a folder, your open files, diagnostics, a spec, a steering file, or terminal output. Or select some code and run Kiro: Ask Kiro from the Command Palette to ask about that selection.
Specs work the same way they do in Kiro IDE. Describe a feature, and Kiro writes the requirements, then a design, then a task list that traces back to both. Fixing a bug instead? A bugfix chat captures what’s broken and what must stay the same before Kiro changes any code.
Each spec document puts its actions where you’d expect them, with buttons in the editor title bar, and CodeLens labels above each task. Run one task to check the work step by step, or run all remaining tasks when you trust the plan. You can review a spec and update its documents as your code changes. See the specs docs for the full workflow.
Kiro workflows come with you too. Give Kiro a task that needs planning, implementation, and review, and workflow agents handle each step in its own session while you keep working in the main chat. Workflows are opt-in, so turn them on in settings before your first run.
Memory lets Kiro remember how you like to work, including your repository’s commands and conventions, corrections you’ve made, and approaches you’ve already ruled out. Turn it on, and Kiro carries that context into later sessions, so you don’t have to explain it again.
You decide how much Kiro does on its own. Approve each action yourself, or turn on approve for me, which lets Kiro approve routine actions, block the ones it judges unsafe, and ask you when it isn’t sure.
When Kiro finishes a turn, you see every file it changed. Open a diff of the whole turn, accept or reject changes file by file, or revert the latest checkpoint.
Kiro also respects VS Code Workspace Trust. In an untrusted folder, Kiro doesn’t start the MCP servers that the workspace defines.
Pick the one that fits how you work today. Both run the same Kiro agent and read the same .kiro setup, so you can switch between them on the same project.
Kiro for VS Code is built to feel like VS Code. Kiro sits in the side bar, its actions live in the Command Palette and CodeLens, and changes open in the diff views you already know. If you’ve spent years tuning VS Code, this is the fastest way to bring Kiro into your day.
Kiro IDE is where we rethink what an IDE looks like as agents take on more development work, and we’ll keep iterating on it with your feedback.
For more on how the Kiro apps fit together, read Which Kiro app should I pick?
- Install Kiro from the VS Code Marketplace or Open VSX.
- Sign in the same way you do in Kiro IDE: with GitHub, Google, AWS Builder ID, or your organization’s identity provider.
- Open a project, open the Kiro tab in the VS Code side bar, and start a Kiro session.
Kiro for VS Code requires VS Code 1.147 or later on macOS, Windows, or Linux. It’s included in every Kiro plan, and your existing plan and billing carry over.
See the Kiro for VS Code docs for setup details, and tell us what you think on Discord.
Your editor, your setup, now with Kiro.