AI News

Kiro Moves Its Coding Agent Into VS Code — No Editor Switch Required, but Check Your Version

November 21, 20260 views阅读中文原文
Kiro Moves Its Coding Agent Into VS Code — No Editor Switch Required, but Check Your Version

TL;DR

Kiro, the spec-driven coding agent from AWS, shipped a native VS Code extension on November 20. It runs on macOS, Windows and Linux, and installs from the Visual Studio Marketplace or Open VSX. Sign in once and the agent lives in your sidebar, with your keybindings, theme and extensions untouched — and no change to your plan or billing.

Two things to check before you bother. First, your VS Code has to be new enough: the docs and the extension manifest both say 1.145 or later, while the blog post says 1.147. Given the disagreement, plan for 1.147 and you will not get stuck. Second, you have to trust the workspace, or the project-level tool configuration simply will not start.

This is not a rewrite of the press release. It is written for the people who actually face the decision: teams where VS Code is the standard and nobody wants to migrate editors just to trial an agent, and developers who want "plan first, then change code" to leave a paper trail instead of scrolling past in a chat window.

What it is

Kiro is not positioned as autocomplete. It works from specs: describe a feature and it writes requirements, then a design, then a task list, with every step traceable back to the input. That workflow used to live only inside Kiro's own IDE; reaching it from VS Code meant wiring things up through something like the Agent Client Protocol. This release turns it into a native extension instead.

After installing, a Kiro panel appears in the sidebar and splits sessions into two kinds:

  • Vibe sessions for a quick question or a small change with no ceremony.
  • Spec sessions for work that needs a plan, producing three documents: requirements, design and task list.

The important compatibility detail is the .kiro folder. If your team already runs Kiro IDE, the extension reads the same directory: specs, steering rules, skills, hooks, Powers and tool-server configuration all carry over without rewriting. Specs also travel both ways — one opened in Kiro IDE shows up in VS Code with its task buttons intact, and one created in VS Code opens in the IDE unchanged.

Context is attached with a hash: typing # lets you pull in a file, a folder, your open files, diagnostics, a Git diff, a spec, a steering file, tool-server prompts, or terminal output. Select some code and run Kiro: Ask Kiro to ask about that selection specifically.

Why it matters

First, it sidesteps an organizational argument entirely. Whether an agent is good often has less to do with the model than with the muscle memory of keybindings, the theme, snippets and a web of interdependent extensions. Telling everyone to move is usually how these projects die. The extension route accepts reality: the agent adapts to people, not the other way around.

Second, two-way spec sync matters more than it sounds. One teammate on Kiro IDE and another on VS Code can share a single spec without copy-paste or version drift. That is the smallest possible implementation of "the tool shouldn't split the team."

Third, each answer shows which steering files it pulled in. Click one to open the source, see why the agent made that choice, and edit the rule on the spot. For something that edits your code on its own, an inspectable rationale is worth more than a few flashy features.

How to use it

  1. Check your VS Code version first. Anything below 1.147 should be upgraded; do not skip this.
  2. Install Kiro from the Marketplace or Open VSX. It requires VS Code 1.145 or later and runs on macOS, Windows or Linux, x64 or arm64.
  3. Sign in. GitHub, Google, AWS Builder ID and your organization's own identity provider all work, the same way they do in Kiro IDE.
  4. Open a local folder and mark the workspace as trusted. Without that, workspace-defined MCP servers will not start and hooks will not run.
  5. Open the Kiro panel in the sidebar and pick vibe or spec.

The spec flow goes like this: describe a feature, Kiro writes requirements, then a design, then a task list with clickable actions on each task. Run one task at a time to inspect the work step by step, or run everything at once if you trust the plan. Bug fixes take a different path: state what is broken and what must stay unchanged before any code moves.

Autonomy defaults to supervised, meaning you approve each action. You can switch to full autopilot, or turn on "approve for me," which lets routine actions through, blocks ones it judges unsafe, and asks you when it is unsure. At the end of each turn you get a list of changed files, a whole-turn diff, per-file accept or reject, and the option to revert to the previous checkpoint.

Two things are off by default and worth knowing: workflows, which hand planning, implementation and review to separate sessions, must be enabled in settings before first use; and memory, which remembers your repository's commands and conventions along with corrections you have made and approaches you already ruled out, is disabled. So if it seems to forget what you told it last time, that is a setting, not a bug.

Who it is for

  • Teams deeply committed to VS Code that cannot realistically migrate.
  • Projects where a plan has to exist before code changes, and that plan has to survive review.
  • Individual developers who prefer approving changes file by file.
  • Mixed teams where some people already run Kiro IDE and others refuse to leave VS Code.

When it is not a good fit

  • Your VS Code is pinned below 1.145 and upgrading is not on the table.
  • You want an agent inside a terminal, a script or a build pipeline. That is Kiro CLI's job, not this extension's.
  • You need airtight post-hoc audit of who approved what. The auto-approval path needs tightening before it meets that bar.
  • You are treating it as a production dependency today. The listing tells its own story: installs are still in the single or low double digits on day one, with two ratings.

Caveats

  • Version mismatch in the docs. The blog post says VS Code 1.147 or later; the docs page and the manifest say 1.145. Go with the stricter number and save yourself a debugging session.
  • Sign-in state is separate. The extension and Kiro IDE each authenticate independently on the same machine.
  • An untrusted workspace is half-broken. In restricted mode, tool servers do not start and hooks do not execute, which reads like a malfunction.
  • Memory and workflows both default to off. Enable them deliberately.
  • Do not bet a critical repo on a day-one build. Run one full spec in a low-stakes project before rolling it out.

Cost and time

The extension is included in every Kiro plan at no extra charge, and existing plans and billing carry over. Current pricing from the official page:

  • Free: $0 per month, 50 credits, open-weight models and Claude Sonnet 4.5.
  • Pro: $20 per user per month, 1,000 credits.
  • Pro+: $40, 2,000 credits.
  • Pro Max: $100, 5,000 credits.
  • Power: $200, 10,000 credits.
  • Add-on credits: $0.04 each.
  • Teams: $20 per seat per month with 500 included credits and shared credit pools.

On time: installing and signing in takes minutes. Finishing a spec depends on scope — a small change often closes in one or two tasks, while a larger feature can split into a dozen or more.

Next steps

First, spend a minute confirming your VS Code version. Below 1.147, upgrade — this is the only trap that wastes an entire session.

Second, pick a repo that does not matter and run one full spec end to end: requirements, design, tasks, review. Judge it less on the quality of the writing and more on whether each step's rationale makes sense to you.

Third, write your steering files as team conventions, not as piled-up prompts. That file decides how the agent thinks by default, and clear beats long.

Sources

  • Official blog: Introducing Kiro for VS Code (November 20, 2026)
  • Official changelog: 1.5.0 Extensions entry (November 19, 2026)
  • Marketplace listing: kiro.kiro-for-vscode, version 1.5.0, updated November 20, 2026
  • Official docs: VS Code extension setup and usage pages (updated November 20, 2026)

Sources

Comments

0 published
Log inorsign up to leave a comment.

Loading comments...