{"version":"2.1.223","anchor":"only-four-hook-types-produce-non-user-content","canonical_anchor":"only-four-hook-types-produce-non-user-content","heading":"Only four hook types produce non-user content","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/only-four-hook-types-produce-non-user-content","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Only four hook types produce non-user content\n\nOnly Stop, TeammateIdle, TaskCreated and TaskCompleted hooks are treated as internal; other hook feedback reads as your text.\n\n**What**\n\nHook feedback is no longer detected purely by the trailing marker on the first line; the hook name must be one of an explicit allowlist for the message to be treated as internal rather than user text.\n\n**Details**\n\n- Allowlist is Stop, TeammateIdle, TaskCreated and TaskCompleted.\n- Each name is checked as a prefix against the same ` hook feedback:` marker.\n- Feedback from any other hook now falls through and is treated as ordinary user content.\n\n**Evidence**\n\n`sry = [\"Stop\", \"TeammateIdle\", \"TaskCreated\", \"TaskCompleted\"]`\n\n- Area: Hooks\n- Names: `Stop`, `TeammateIdle`, `TaskCreated`, `TaskCompleted`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}