Answer: Validate each migrated agent configuration from your shell with the agent validate command, then start or return to a V3 session in the migrated workspace and run /config and /hooks to confirm Kiro loaded the expected agents, permissions, and Hooks. Also exercise representative commands to verify the approval behavior you intended, and resolve every conversion warning or validation error before using the configuration in CI. Status: Confirmed Entry: tool/kiro/troubleshooting/validate-migration Revision: 1 Digest: sha256:0e549f094147668a (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:16Z Last changed: 2026-11-13T03:37:16Z Last verified: 2026-11-20T13:21:04Z Next check: 2026-11-21T13:21:04Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of validation command | kiro-cli agent validate --path .kiro/agents/my-agent.json | [1] | 2026-11-20 session check commands | /config and /hooks | [1] | 2026-11-20 final step | Resolve every conversion warning or validation error | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Migration guide - Upgrade from CLI 2.x - CLI - Docs - Kiro". https://kiro.dev/docs/cli/v3/migration-guide/ Role: primary. Accessed: 2026-11-20T13:21:04Z Quote: "kiro-cli agent validate --path .kiro/agents/my-agent.json" (Supports: validation command) Quote: "Run /config and /hooks to confirm Kiro loaded the expected agents, permissions, and Hooks." (Supports: session check commands) Quote: "Resolve every conversion warning or validation error before using the configuration in CI." (Supports: final step) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 475b86970159f5a5debfbe4b6506675ab3283d78fde7186559a147163f52ae74 (captured 2026-11-20T13:21:02Z) 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:21:04Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:21:04Z Last attempt: 2026-11-20T13:21:04Z Notes and limitations: Extracted automatically from a single official source (section "7. Validate your migration"). Related: 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/verify-vpc-connection How do I verify or troubleshoot a Kiro VPC connection? 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/kiro/troubleshooting/v3-breaking-changes What breaking changes does Kiro CLI V3 introduce compared to 2.x? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:37:16Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/troubleshooting/validate-migration/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/validate-migration POST: https://latestn.com/dispute/tool/kiro/troubleshooting/validate-migration with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/troubleshooting/validate-migration?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I validate that my Kiro CLI 2.x to V3 migration succeeded? Revision 1, last verified 2026-11-20T13:21:04Z. https://latestn.com/tool/kiro/troubleshooting/validate-migration (accessed 2026-11-21T09:59:53Z). @misc{LatestN_tool_kiro_troubleshooting_validate_migration_r1, title = {How do I validate that my Kiro CLI 2.x to V3 migration succeeded?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/troubleshooting/validate-migration}}, note = {Revision 1; digest sha256:0e549f094147668a; last verified 2026-11-20T13:21:04Z; accessed 2026-11-21T09:59:53Z} } 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/validate-migration