Answer: Open the Agent Hooks section in the Kiro panel, then click the upgrade icon badge on each unmigrated hook to convert it to the v1 format; the migrated hook becomes active immediately. Legacy userTriggered Hooks are the exception: they are not migrated to the v1 schema and continue to work as legacy Hooks. Status: Confirmed Entry: tool/kiro/agents-and-automation/migrate-hooks Revision: 1 Digest: sha256:e31ec047775d197f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:43:03Z Last changed: 2026-11-13T03:43:03Z Last verified: 2026-11-20T13:29:57Z Next check: 2026-11-21T13:29:57Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of migration method | Click it to convert the hook to the v1 format | [1] | 2026-11-20 location | Agent Hooks section in the Kiro panel | [1] | 2026-11-20 post-migration status | active immediately | [1] | 2026-11-20 legacy files | remain on disk after migration but are no longer loaded | [1] | 2026-11-20 exception | Legacy userTriggered Hooks | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "What's new in 1.0 - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/whats-new-v1/ Role: primary. Accessed: 2026-11-20T13:29:57Z Quote: "Each unmigrated hook displays a badge with an upgrade icon. Click it to convert the hook to the v1 format." (Supports: migration method) Quote: "Open the Agent Hooks section in the Kiro panel." (Supports: location) Quote: "The migrated hook becomes active immediately." (Supports: post-migration status) Quote: "Original legacy files remain on disk after migration but are no longer loaded." (Supports: legacy files) Quote: "Legacy userTriggered Hooks are the exception: they are not migrated to the v1 schema and continue to work as legacy Hooks." (Supports: exception) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 30146bdc0d4de2180f3117e225aa30ce513c2cf42ccc4d899c5ac39609048068 (captured 2026-11-20T13:29:58Z) 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:29:57Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:29:57Z Last attempt: 2026-11-20T13:29:57Z Notes and limitations: Extracted automatically from a single official source (section "Migrating hooks"). Related: https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks-profile-scoped-format How do I migrate Kiro CLI 2.x hooks to the current profile-scoped format? 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/migrate-agent-config-to-v3 How do I migrate my Kiro CLI 2.x agent configuration to CLI V3? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:43:03Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks/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 POST: https://latestn.com/dispute/tool/kiro/agents-and-automation/migrate-hooks 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?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I migrate my existing hooks to Kiro IDE 1.0? Revision 1, last verified 2026-11-20T13:29:57Z. https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks (accessed 2026-11-21T10:04:16Z). @misc{LatestN_tool_kiro_agents_and_automation_migrate_hooks_r1, title = {How do I migrate my existing hooks to Kiro IDE 1.0?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks}}, note = {Revision 1; digest sha256:e31ec047775d197f; last verified 2026-11-20T13:29:57Z; accessed 2026-11-21T10:04:16Z} } 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