What's new in 3.0 - CLI - Docs - Kiro Loading image... Product * About Kiro * IDE * CLI * Web * Mobile * Crew * 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 * * * * * * * English Site Terms License Responsible AI Policy Legal Privacy Policy Cookie Preferences English Loading image... * Apps * CLI * Web * Enterprise * Pricing * Docs * Community * Resources SIGN IN DOWNLOADS Loading image... Get Started Installation Authentication Your first project Models Overview Available models Reasoning effort Features How Kiro works Specs Steering Hooks MCP Permissions Custom agents Agent Skills Powers Cloud sessions Compaction Kiroignore Checkpoints and rewind Built-in tools Configuration scopes IDE 1.x What's new in 1.0 Setup & First Run Editor Chat Experimental Troubleshooting 0.x reference CLI What's new in 3.0 Migration guide Upgrading agent configs Permissions migration Hooks migration Agent config changes New features in 3.0 Tangent Setup & First Run Terminal UI Chat Voice mode Headless mode ACP Auto complete Experimental 2.x reference Crew Quick start Installation Running 24/7 Chat Agent Capabilities Features Interfaces Apps System & storage Configuration Security Troubleshooting Web Setup & First Run Identity Center Connect your repositories Working with the agent Autonomous mode Automations Memory Configuration Sync Sandbox Mobile - Preview Overview Commands and Reference CLI commands Slash commands Built-in tools Exit codes Settings Billing Overview Managing your subscription Upgrading your plan Downgrading your plan Cancelling your plan Purchasing add-on credits Managing your payments Managing usage notifications Managing your taxes Contacting billing support Deleting your account Related questions Enterprise Concepts Onboarding quickstart Connecting your identity provider Deployment options Subscribe your team Manage subscriptions Governance Monitor and track Settings Managed updates Billing IAM Supported regions Privacy and Security Overview Data protection Code references Compliance validation Infrastructure security IAM permissions Firewalls, proxies, and data perimeters VPC endpoints (AWS PrivateLink) Guides Overview Language support Learn by playing Migration Migrating from Q Developer Migrating from VSCode Upgrading from Q CLI * Docs * * CLI * * What's new in 3.0 Copy page View as Markdown What's new in CLI 3.0 Copy page View as Markdown 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 harness 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 harness (new tools, better planning, smarter tool selection) now ships to all clients simultaneously, and your .kiro configuration is portable across all surfaces. 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. 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 → Tangent — branch your conversation into side-conversations that inherit your context, explore freely, then jump back to exactly where you left off. Use /tangent to branch. Learn more → Feature overview Feature Status Change from 2.x Action needed Chat (Default mode) ✅ Available Renamed from "Vibe" None Spec-driven development ✅ New Built-in Spec agent None Plan mode ✅ New New built-in agent (Shift+Tab) None Tangent ✅ New Named, nestable side-conversations None Custom agents ⬆️ Enhanced Tags replace tool IDs; toolsSettings → permissions ⚠️ Migrate Steering ✅ Available Front matter metadata added None Hooks ✅ Available New JSON schema, standalone files ⚠️ Migrate Permissions ✅ New Replaces trust flags ⚠️ Migrate MCP servers ✅ Available OAuth, disabledTools, autoApprove added None Skills ✅ Available Unchanged None Powers ✅ Available Auto-pickup from IDE None Sub-agents ✅ Available Single-agent UI (was multi-monitor) None Compaction ✅ Available Manual /compact + improved auto None Session export ✅ New New capability None Trusted workspaces ✅ New New capability None Code Intelligence ✅ Available Client-vended LSP tool None Knowledge ✅ Available Semantic indexing None Todo ⚠️ Gated Available but visualization pending None aws_tool ❌ Removed Use MCP servers ⚠️ Migrate Breaking changes Change Previous (2.x) New (3.0) Impact aws_tool removed Built-in AWS tool Use MCP servers for AWS access High Session format changed v2 session format v3 session format (not backward-compatible) High — back up ~/.kiro/sessions/ before upgrading Hook format changed Hooks embedded in agent config Standalone .kiro/hooks/*.json files High Hook trigger names camelCase ( agentSpawn ) PascalCase ( SessionStart ) High Tool IDs standardized camelCase ( readFile , writeFile ) snake_case with short aliases Medium Sub-agent UI simplified Multi-agent monitor (Ctrl+G) Single-agent UI — sub-agents run in background Medium Trust model replaced --trust-all-tools , /tools trust Capability-based permissions.yaml High "Vibe" concept removed N/A for CLI "Default" mode is the standard name Low Migration guide Follow these steps in order. The most impactful changes are permissions and hooks — both require manual migration. * Full migration guide — all 6 steps with examples * Permissions migration — trust flags → permissions.yaml , behavioral changes * Hooks migration — embedded hooks → .kiro/hooks/ , trigger name mapping * Agent config changes — new fields and Markdown format * New features — plan mode, powers auto-pickup, skills, compaction, trusted workspaces, built-in tools Info To convert your existing V2 agent configurations to the universal V2+V3 format, run /upgrade-agent inside a V3 session. See Upgrading agent configs for details. Known gaps Gap Detail AL2 not supported CLI 3.0 does not run on Amazon Linux 2. Use CLI 2.x if your environment requires AL2. Classic mode not supported The legacy non-TUI mode ( kiro-cli chat without the TUI) does not support the v3 engine. Use the TUI. Session resume V3 sessions cannot be resumed in V2. If you switch back to the V2 engine, previously created V3 sessions will not be available. Learn more * kiro-cli diagnostic — diagnostics and environment validation * kiro-cli issue — file a bug report * Hooks documentation — full hooks reference * MCP configuration — MCP server setup * Steering — steering document details Page updated: August 4, 2026 CLI Migration guide