Answer: Use /upgrade-agent, which rewrites known CLI 2.x names to shared groups (for example, fs_read becomes read, and execute_cmd becomes shell), and it warns when a group covers more tools than the old name. Status: Confirmed Entry: tool/kiro/agents-and-automation/migrate-tool-matchers Revision: 3 Digest: sha256:a5028ccfd60f3c34 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:12Z Last changed: 2026-11-20T13:21:01Z (Array-form matchers: — → Array-form matchers that are valid V3 tool IDs stay as authored.) Last verified: 2026-11-20T13:21:01Z Next check: 2026-11-21T13:21:01Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Migration command | /upgrade-agent | [1] | 2026-11-20 Example rewrite (read) | fs_read becomes read | [1] | 2026-11-20 Example rewrite (shell) | execute_cmd becomes shell | [1] | 2026-11-20 Warning behavior | It warns when a group covers more tools than the old name. | [1] | 2026-11-20 fs_read rewrite scope | The fs_read rewrite also matches grep , glob , code , introspect , and tool_search | [1] | 2026-11-20 Array-form matchers | Array-form matchers that are valid V3 tool IDs stay as authored. | [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:21:01Z Quote: "/upgrade-agent rewrites known CLI 2.x names to shared groups." (Supports: Migration command) Quote: "For example, fs_read becomes read , and execute_cmd becomes shell ." (Supports: Example rewrite (read), Example rewrite (shell)) Quote: "It warns when a group covers more tools than the old name." (Supports: Warning behavior) Quote: "The fs_read rewrite also matches grep , glob , code , introspect , and tool_search ." (Supports: fs_read rewrite scope) Quote: "Array-form matchers that are valid V3 tool IDs stay as authored." (Supports: Array-form matchers) 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:21:01Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:21:01Z Last attempt: 2026-11-20T13:21:01Z Notes and limitations: Extracted automatically from a single official source (section "Migrate tool matchers"). Related: 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/monitor-autonomous-mode-progress How do I monitor progress and review the pull request in Kiro autonomous mode? https://latestn.com/tool/kiro/agents-and-automation/move-bot-to-another-install How do I move a Kiro bot to another install? 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/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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:21:01Z | changed | Array-form matchers: — → Array-form matchers that are valid V3 tool IDs stay as authored. | [1] 2026-11-20T13:21:01Z | changed | fs_read rewrite scope: — → The fs_read rewrite also matches grep , glob , code , introspect , and tool_search | [1] 2026-11-20T13:21:01Z | changed | Warning behavior: — → It warns when a group covers more tools than the old name. | [1] 2026-11-20T13:21:01Z | changed | Example rewrite (shell): — → execute_cmd becomes shell | [1] 2026-11-20T13:21:01Z | changed | Example rewrite (read): — → fs_read becomes read | [1] 2026-11-20T13:21:01Z | changed | Migration command: — → /upgrade-agent | [1] 2026-11-20T13:21:01Z | changed | array-form matchers: Array-form matchers that are valid V3 tool IDs stay as authored. → — | [1] 2026-11-20T13:21:01Z | changed | warning behavior: It warns when a group covers more tools than the old name. → — | [1] 2026-11-20T13:21:01Z | changed | second example rewrite: execute_cmd becomes shell → — | [1] 2026-11-20T13:21:01Z | changed | example rewrite: fs_read becomes read → — | [1] 2026-11-20T13:21:01Z | changed | migration command: /upgrade-agent → — | [1] 2026-11-17T13:42:16Z | changed | array-form matchers: — → Array-form matchers that are valid V3 tool IDs stay as authored. | [1] 2026-11-17T13:42:16Z | changed | warning behavior: — → It warns when a group covers more tools than the old name. | [1] 2026-11-17T13:42:16Z | changed | second example rewrite: — → execute_cmd becomes shell | [1] 2026-11-17T13:42:16Z | changed | example rewrite: — → fs_read becomes read | [1] 2026-11-17T13:42:16Z | changed | migration command: — → /upgrade-agent | [1] 2026-11-17T13:42:16Z | changed | Array-form matchers: Array-form matchers that are valid V3 tool IDs stay as authored. → — | [1] 2026-11-17T13:42:16Z | changed | fs_read rewrite scope: The fs_read rewrite also matches grep , glob , code , introspect , and tool_search . → — | [1] 2026-11-17T13:42:16Z | changed | Warning behavior: It warns when a group covers more tools than the old name. → — | [1] 2026-11-17T13:42:16Z | changed | Example rewrite (shell): execute_cmd becomes shell → — | [1] 2026-11-17T13:42:16Z | changed | Example rewrite (read): fs_read becomes read → — | [1] 2026-11-17T13:42:16Z | changed | Migration command: /upgrade-agent → — | [1] 2026-11-13T03:37:12Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/agents-and-automation/migrate-tool-matchers/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-tool-matchers POST: https://latestn.com/dispute/tool/kiro/agents-and-automation/migrate-tool-matchers with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/agents-and-automation/migrate-tool-matchers?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I migrate tool matchers in Kiro CLI hooks? Revision 3, last verified 2026-11-20T13:21:01Z. https://latestn.com/tool/kiro/agents-and-automation/migrate-tool-matchers (accessed 2026-11-21T10:04:55Z). @misc{LatestN_tool_kiro_agents_and_automation_migrate_tool_matchers_r3, title = {How do I migrate tool matchers in Kiro CLI hooks?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/agents-and-automation/migrate-tool-matchers}}, note = {Revision 3; digest sha256:a5028ccfd60f3c34; last verified 2026-11-20T13:21:01Z; accessed 2026-11-21T10:04:55Z} } 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-tool-matchers