Answer: From a V3 session, run /upgrade-agent to convert your V2 agent configuration, then run /upgrade-agent diagnostics and review the report before editing files manually. The command backs up selected profiles, converts compatible permission and Hook fields, and reports anything that needs manual attention. Status: Confirmed Entry: tool/kiro/agents-and-automation/migrate-agent-config-to-v3 Revision: 2 Digest: sha256:b08642c51639c222 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:15Z Last changed: 2026-11-20T13:21:02Z (Hook trigger mapping (CLI 2.x to CLI V3): — → agentSpawn SessionStart) Last verified: 2026-11-20T13:21:02Z Next check: 2026-11-21T13:21:02Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Migration command | /upgrade-agent | [1] | 2026-11-20 Diagnostics command | /upgrade-agent diagnostics | [1] | 2026-11-20 What the command does | backs up selected profiles, converts compatible permission and Hook fields, and reports anything that needs manual attention | [1] | 2026-11-20 Re-run after changing V2 trust settings | /upgrade-agent | [1] | 2026-11-20 Hook trigger mapping (CLI 2.x to CLI V3) | agentSpawn SessionStart | [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:02Z Quote: "From the V3 session, run the conversion and review its diagnostics before editing files manually: > /upgrade-agent" (Supports: Migration command) Quote: "> /upgrade-agent diagnostics" (Supports: Diagnostics command) Quote: "The command backs up selected profiles, converts compatible permission and Hook fields, and reports anything that needs manual attention." (Supports: What the command does) Quote: "Run /upgrade-agent again after changing V2 trust settings so the generated V3 rules stay current." (Supports: Re-run after changing V2 trust settings) Quote: "agentSpawn SessionStart" (Supports: Hook trigger mapping (CLI 2.x to CLI V3)) 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:02Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:21:02Z Last attempt: 2026-11-20T13:21:02Z Notes and limitations: Extracted automatically from a single official source (section "2. Run /upgrade-agent"). Related: https://latestn.com/tool/kiro/agents-and-automation/migrate-agent-config-v1 How do I migrate my Kiro agent configuration to the new format in version 1.0? https://latestn.com/tool/kiro/agents-and-automation/migrate-hook-triggers How do I migrate Kiro hooks from 0.x trigger names to 1.0? https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks How do I migrate my existing hooks to Kiro IDE 1.0? https://latestn.com/tool/kiro/agents-and-automation/manage-installed-templates How do I manage installed agent templates in Kiro Crew? https://latestn.com/tool/kiro/agents-and-automation/manage-prompts How do I manage prompts in Kiro Crew, from the dashboard or the filesystem? https://latestn.com/tool/kiro/agents-and-automation/manifest-cron-scheduling How do I schedule a Kiro Crew app with cron jobs in the manifest? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:21:02Z | changed | Hook trigger mapping (CLI 2.x to CLI V3): — → agentSpawn SessionStart | [1] 2026-11-20T13:21:02Z | changed | Re-run after changing V2 trust settings: — → /upgrade-agent | [1] 2026-11-20T13:21:02Z | changed | Standalone hooks location: .kiro/hooks/*.json → — | [1] 2026-11-20T13:21:02Z | changed | Recommended casing: PascalCase → — | [1] 2026-11-20T13:21:02Z | changed | Legacy trigger alias: camelCase → — | [1] 2026-11-20T13:21:02Z | changed | Hook conversion format: flat array of Hook documents → — | [1] 2026-11-20T13:21:02Z | changed | Re-run after trust changes: /upgrade-agent → — | [1] 2026-11-13T03:37:15Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/agents-and-automation/migrate-agent-config-to-v3/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/agents-and-automation/migrate-agent-config-to-v3 POST: https://latestn.com/dispute/tool/kiro/agents-and-automation/migrate-agent-config-to-v3 with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/agents-and-automation/migrate-agent-config-to-v3?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I migrate my Kiro CLI 2.x agent configuration to CLI V3? Revision 2, last verified 2026-11-20T13:21:02Z. https://latestn.com/tool/kiro/agents-and-automation/migrate-agent-config-to-v3 (accessed 2026-11-21T10:05:19Z). @misc{LatestN_tool_kiro_agents_and_automation_migrate_agent_config_to_v3_r2, title = {How do I migrate my Kiro CLI 2.x agent configuration to CLI V3?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/agents-and-automation/migrate-agent-config-to-v3}}, note = {Revision 2; digest sha256:b08642c51639c222; last verified 2026-11-20T13:21:02Z; accessed 2026-11-21T10:05:19Z} } 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/agents-and-automation/migrate-agent-config-to-v3