Answer: Use /upgrade-agent, which flattens the legacy object into an array in the agent profile, giving each Hook a name and keeping the compatible camelCase trigger alias. The converter preserves array-form Hooks and drops a Hook that V3 cannot represent, reporting a warning instead of writing an invalid profile. Status: Confirmed Entry: tool/kiro/agents-and-automation/migrate-hooks-profile-scoped-format Revision: 2 Digest: sha256:66bb4045d04bd7ad (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:11Z Last changed: 2026-11-18T13:17:28Z (Example matcher: — → read) Last verified: 2026-11-20T13:20:59Z Next check: 2026-11-21T13:20:59Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Migration command | /upgrade-agent | [1] | 2026-11-20 Example timeout | 10 | [1] | 2026-11-20 Example trigger | agentSpawn | [1] | 2026-11-20 Example matcher | read | [1] | 2026-11-20 Unrepresentable Hook handling | drops a Hook that V3 cannot represent | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Hooks migration - Upgrade from CLI 2.x - CLI - Docs - Kiro". https://kiro.dev/docs/cli/v3/hooks-migration/ Role: primary. Accessed: 2026-11-20T13:20:59Z Quote: "Current profile-scoped format /upgrade-agent flattens the legacy object into an array in the agent profile." (Supports: Migration command) Quote: ""timeout" : 10 } , { "name" : "preToolUse-0"" (Supports: Example timeout) Quote: ""trigger" : "agentSpawn"" (Supports: Example trigger) Quote: ""matcher" : "read"" (Supports: Example matcher) Quote: "It drops a Hook that V3 cannot represent and reports a warning instead of writing an invalid profile." (Supports: Unrepresentable Hook handling) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 42a3f96b2d7f54d28aae6bcb77671bf6460a3c962fd70e375b80accca0b06679 (captured 2026-11-20T13:21:00Z) 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:59Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:20:59Z Last attempt: 2026-11-20T13:20:59Z Notes and limitations: Extracted automatically from a single official source (section "Current profile-scoped format"). Related: https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks-standalone-file-format How do I migrate Kiro CLI hooks to the current standalone file format? https://latestn.com/tool/kiro/agents-and-automation/migrate-tool-matchers How do I migrate tool matchers in Kiro CLI hooks? https://latestn.com/tool/kiro/agents-and-automation/modify-thinking-behavior-mcp How can I modify Kiro's thinking behavior with MCP? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:17:28Z | changed | Example matcher: — → read | [1] 2026-11-18T13:17:28Z | changed | Example trigger: — → agentSpawn | [1] 2026-11-18T13:17:28Z | changed | Example timeout: — → 10 | [1] 2026-11-18T13:17:28Z | changed | Unrepresentable Hook handling: It drops a Hook that V3 cannot represent and reports a warning instead of writing an invalid profile. → drops a Hook that V3 cannot represent | [1] 2026-11-18T13:17:28Z | changed | Matcher example: read → — | [1] 2026-11-18T13:17:28Z | changed | Timeout example: 10 → — | [1] 2026-11-18T13:17:28Z | changed | Trigger example: agentSpawn → — | [1] 2026-11-18T13:17:28Z | changed | Hook name example: agentSpawn-0 → — | [1] 2026-11-13T03:37:11Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks-profile-scoped-format/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-hooks-profile-scoped-format POST: https://latestn.com/dispute/tool/kiro/agents-and-automation/migrate-hooks-profile-scoped-format with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/agents-and-automation/migrate-hooks-profile-scoped-format?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I migrate Kiro CLI 2.x hooks to the current profile-scoped format? Revision 2, last verified 2026-11-20T13:20:59Z. https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks-profile-scoped-format (accessed 2026-11-21T10:04:54Z). @misc{LatestN_tool_kiro_agents_and_automation_migrate_hooks_profile_scoped_format_r2, title = {How do I migrate Kiro CLI 2.x hooks to the current profile-scoped format?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks-profile-scoped-format}}, note = {Revision 2; digest sha256:66bb4045d04bd7ad; last verified 2026-11-20T13:20:59Z; accessed 2026-11-21T10:04:54Z} } 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-hooks-profile-scoped-format