Answer: Kiro CLI V3 introduces several breaking changes compared to 2.x, including removal of the built-in AWS tool (use_aws/aws) in favor of MCP servers for AWS access, a separate V3 session store, a new PascalCase hook format and trigger names, capability-based permissions.yaml instead of per-tool toolsSettings, stricter sub-agent tool call checks against the parent session, retirement of the Classic interface, retirement of the desktop app and inline autocomplete, and removal of several desktop-app commands. Status: Confirmed Entry: tool/kiro/troubleshooting/v3-breaking-changes Revision: 1 Digest: sha256:297ded163e0dcf58 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:08Z Last changed: 2026-11-13T03:37:08Z Last verified: 2026-11-20T13:20:55Z Next check: 2026-11-21T13:20:55Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Built-in AWS tool | Use MCP servers for AWS access | [1] | 2026-11-20 Session format | Separate V3 session store | [1] | 2026-11-20 Hook format | PascalCase array definitions, inline or in standalone .kiro/hooks/*.json files | [1] | 2026-11-20 Hook trigger names | PascalCase ( SessionStart ) | [1] | 2026-11-20 Persistent trust configuration | Capability-based permissions.yaml | [1] | 2026-11-20 Sub-agent tool calls | A sub-agent's tool call runs without a prompt only when the parent session's policy also allows it | [1] | 2026-11-20 Classic interface | Classic interface retired | [1] | 2026-11-20 Desktop app and inline autocomplete | Desktop app and inline autocomplete retired | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Upgrade from CLI 2.x - CLI - Docs - Kiro". https://kiro.dev/docs/cli/v3/ Role: primary. Accessed: 2026-11-20T13:20:55Z Quote: "CLI 2.x use_aws tool (preferred alias aws ) Use MCP servers for AWS access" (Supports: Built-in AWS tool) Quote: "V2 session store Separate V3 session store" (Supports: Session format) Quote: "CamelCase object embedded in the profile PascalCase array definitions, inline or in standalone .kiro/hooks/*.json files" (Supports: Hook format) Quote: "camelCase ( agentSpawn ) PascalCase ( SessionStart )" (Supports: Hook trigger names) Quote: "Per-tool toolsSettings rules Capability-based permissions.yaml" (Supports: Persistent trust configuration) Quote: "A sub-agent's tool call runs without a prompt only when the parent session's policy also allows it" (Supports: Sub-agent tool calls) Quote: "Classic interface retired" (Supports: Classic interface) Quote: "Desktop app and inline autocomplete retired" (Supports: Desktop app and inline autocomplete) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: da3ff0cce495bb41ba49132a77436e40f4570eb67dbd53921b1f59f7b60ba15f (captured 2026-11-20T13:20:52Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:20:55Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:20:55Z Last attempt: 2026-11-20T13:20:55Z Notes and limitations: Extracted automatically from a single official source (section "Breaking changes"). Related: https://latestn.com/tool/kiro/troubleshooting/validate-migration How do I validate that my Kiro CLI 2.x to V3 migration succeeded? https://latestn.com/tool/kiro/troubleshooting/verify-on-demand-loading How do I verify that on-demand tool loading is working in Kiro? https://latestn.com/tool/kiro/troubleshooting/verify-permission-policy How do I verify a Kiro permission policy is applied and handle validation errors? https://latestn.com/tool/kiro/troubleshooting/troubleshoot-settings How do I reset Kiro settings or fix invalid setting values? https://latestn.com/tool/kiro/troubleshooting/troubleshoot-until-verified-workflow How do I troubleshoot until a fix is verified using a Kiro workflow? https://latestn.com/tool/kiro/troubleshooting/unexpected-hook-behavior How do I fix unexpected behavior from a Kiro hook? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:37:08Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/v3-breaking-changes/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/troubleshooting/v3-breaking-changes POST: https://latestn.com/dispute/tool/kiro/troubleshooting/v3-breaking-changes with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/v3-breaking-changes?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What breaking changes does Kiro CLI V3 introduce compared to 2.x? Revision 1, last verified 2026-11-20T13:20:55Z. https://latestn.com/tool/kiro/troubleshooting/v3-breaking-changes (accessed 2026-11-21T09:56:49Z). @misc{LatestN_tool_kiro_troubleshooting_v3_breaking_changes_r1, title = {What breaking changes does Kiro CLI V3 introduce compared to 2.x?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/v3-breaking-changes}}, note = {Revision 1; digest sha256:297ded163e0dcf58; last verified 2026-11-20T13:20:55Z; accessed 2026-11-21T09:56:49Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/troubleshooting/v3-breaking-changes