Answer: The text only describes legacy manual Hooks (IDE only); it does not describe Manual (CLI V3) hooks, so no difference between the two can be stated from this text. Legacy manual Hooks created in IDE 0.x continue to appear in the Agent Hooks panel with a legacy label, remain runnable if enabled, and new Manual-trigger Hooks can't be created in the IDE. Status: Confirmed Entry: tool/kiro/features/manual-vs-legacy-hooks Revision: 2 Digest: sha256:50261ff3dc01f380 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:42:12Z Last changed: 2026-11-18T13:23:52Z (IDE on-demand alternative: — → manually included Steering file) Last verified: 2026-11-20T13:28:41Z Next check: 2026-11-21T13:28:41Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of legacy manual hooks label | legacy label | [1] | 2026-11-20 legacy manual hooks runnability | remain runnable | [1] | 2026-11-20 IDE version | IDE 0.x | [1] | 2026-11-20 new manual-trigger hook creation | you can't create a new Manual-trigger Hook in the IDE | [1] | 2026-11-20 IDE on-demand alternative | manually included Steering file | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Hook triggers - Hooks - Features - Docs - Kiro". https://kiro.dev/docs/hooks/types/ Role: primary. Accessed: 2026-11-20T13:28:41Z Quote: "continue to appear in the Agent Hooks panel with a legacy label" (Supports: legacy manual hooks label) Quote: "Enabled legacy manual Hooks remain runnable using the play button next to the Hook name or Start Hook in the Hook view." (Supports: legacy manual hooks runnability) Quote: "Manual Hooks created in IDE 0.x" (Supports: IDE version) Quote: "you can't create a new Manual-trigger Hook in the IDE" (Supports: new manual-trigger hook creation) Quote: "For a new IDE on-demand workflow, create a manually included Steering file" (Supports: IDE on-demand alternative) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: ca71d565da91daa04e6aebab87f05edf52a7429e6798d193ff2eb61ab5a678fc (captured 2026-11-20T13:28:40Z) 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:28:41Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:28:41Z Last attempt: 2026-11-20T13:28:41Z Notes and limitations: Extracted automatically from a single official source (section "Legacy manual Hooks (IDE only)"). Related: https://latestn.com/tool/kiro/features/mcp-prompts-with-arguments How do I use MCP prompts and pass arguments to them in Kiro? https://latestn.com/tool/kiro/features/merge-tangent-back How do I merge a tangent back into the main Kiro CLI chat session? https://latestn.com/tool/kiro/features/mobile-access-setup How do I set up mobile access to Kiro Crew and how long do sessions last? https://latestn.com/tool/kiro/features/manage-cloud-sessions How do I manage cloud sessions in Kiro? https://latestn.com/tool/kiro/features/manage-instances How do I manage or remove instances in a Kiro crew? https://latestn.com/tool/kiro/features/managed-vs-attached-browsers What is the difference between managed and attached browsers in Kiro Crew? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:23:52Z | changed | IDE on-demand alternative: — → manually included Steering file | [1] 2026-11-18T13:23:52Z | changed | new manual-trigger hook creation: — → you can't create a new Manual-trigger Hook in the IDE | [1] 2026-11-18T13:23:52Z | changed | legacy manual hooks runnability: — → remain runnable | [1] 2026-11-18T13:23:52Z | changed | legacy manual hooks label: — → legacy label | [1] 2026-11-18T13:23:52Z | changed | creation restriction: you can't create a new Manual-trigger Hook in the IDE → — | [1] 2026-11-18T13:23:52Z | changed | legacy label: legacy label → — | [1] 2026-11-18T13:23:52Z | changed | legacy manual Hooks scope: IDE only → — | [1] 2026-11-13T03:42:12Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/features/manual-vs-legacy-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/features/manual-vs-legacy-hooks POST: https://latestn.com/dispute/tool/kiro/features/manual-vs-legacy-hooks with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/features/manual-vs-legacy-hooks?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What is the difference between legacy manual hooks and Manual (CLI V3) hooks in Kiro? Revision 2, last verified 2026-11-20T13:28:41Z. https://latestn.com/tool/kiro/features/manual-vs-legacy-hooks (accessed 2026-11-21T10:04:01Z). @misc{LatestN_tool_kiro_features_manual_vs_legacy_hooks_r2, title = {What is the difference between legacy manual hooks and Manual (CLI V3) hooks in Kiro?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/features/manual-vs-legacy-hooks}}, note = {Revision 2; digest sha256:50261ff3dc01f380; last verified 2026-11-20T13:28:41Z; accessed 2026-11-21T10:04:01Z} } 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/features/manual-vs-legacy-hooks