Loading image...Kiro
  • CLI
  • Web
  • Enterprise
  • Pricing
  • Docs
SIGN INDOWNLOADS
Loading image...Kiro
Loading image...Kiro
Product
  • About Kiro
  • CLI
  • Web
  • Pricing
  • Downloads
For
  • Enterprise
  • Startups
  • Students
Community
  • Overview
  • Ambassadors
  • Discord
  • Events
  • Powers
  • Shop
  • Showcase
Resources
  • Docs
  • Blog
  • Changelog
  • FAQs
  • Report a bug
  • Suggest an idea
  • Billing support
Social
Site TermsLicenseResponsible AI PolicyLegalPrivacy PolicyCookie Preferences
  1. Docs
  2. CLI
  3. V3

CLI 3.0 (Early Access)


Info

An early release of Kiro CLI v3 is now available. Try it out with: kiro-cli --v3. V3 runs alongside your existing 2.x install -- your current setup is unchanged until you opt in.

A single engine for all Kiro surfaces

CLI 3.0 is built on the same unified agent harness that powers the Kiro IDE and Kiro Web. Every improvement to the engine (new tools, better planning, smarter tool selection) now ships to all clients simultaneously.

What's new in 3.0

Spec-driven development -- the Spec agent brings structured development to the terminal. Define requirements, generate designs, execute task plans with checkpoints. Use /spec new <name> to start. Learn more →

Capability-based permissions -- declare structured policies in permissions.yaml for fine-grained, auditable control. One rule can allow or deny an entire category of operations across all tools. Learn more →

Enhanced hooks -- standalone .kiro/hooks/*.json files with two action types (shell commands and agent prompts), new triggers, and a versioned schema. Learn more →

Enhanced agent config -- tag-based tool selection, unified permissions block, Markdown format, inline MCP servers. Learn more →

Breaking changes

AreaWhat changed
Permissions--trust-all-tools and /tools trust replaced by permissions.yaml
HooksEmbedded hooks moved to standalone .kiro/hooks/*.json, PascalCase triggers
Agent configtoolsSettings replaced by permissions field, tool IDs replaced by tags
aws_toolRemoved -- use MCP servers instead
Session formatv3 format not backward-compatible -- back up ~/.kiro/sessions/
Supervised modeRemoved -- use permissions.yaml

Get started

Try the v3 engine: kiro-cli --v3.

  • Permissions -- capability-based permission model
  • Hooks -- standalone hooks with new triggers
  • Agent config -- tags, permissions block, Markdown format
  • Specs -- spec-driven development in the terminal
  • Feature comparison -- full v2 → v3 feature status table
Info

A migration guide for converting v2 configurations is coming soon.

Known gaps

GapDetail
AL2 not supportedCLI 3.0 does not run on Amazon Linux 2. Use CLI 2.x if your environment requires AL2.
Classic mode not supportedThe legacy non-TUI mode (kiro-cli chat without the TUI) does not support the v3 engine. Use the TUI.

Learn more

  • kiro-cli diagnostic -- validates your environment
  • Hooks documentation -- full hooks reference
  • MCP configuration -- MCP server setup
  • Steering -- steering document details
Page updated: June 17, 2026
Migrating from Q Developer
Specs