{"version":"2.1.242","anchor":"hook-events-are-tagged-by-where-they-could-run","canonical_anchor":"hook-events-are-tagged-by-where-they-could-run","heading":"Hook events are tagged by where they could run","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/hook-events-are-tagged-by-where-they-could-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Hook events are tagged by where they could run\n\nEach hook event is now labelled by where it should run: locally, deferred, low value or container-internal.\n\n**What**\n\nA new table labels each hook event with where it belongs: session start, session end and notification hooks run locally; permission requests are deferred; setup, compaction, teammate-idle, task and elicitation hooks are marked low value; and config, worktree, instructions, directory, file-change and message-display events are marked internal to the container.\n\n**Details**\n\n- The table is classification data with no user-facing surface, and reads as triage for which events a separate hooks worker would be handed.\n- No flag or code path was observed acting on the labels in this build.\n\n**Evidence**\n\n`container_internal`\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}