{"version":"2.1.299","anchor":"hook-registration-gate-tied-to-tengu-melodic-ember","canonical_anchor":"hook-registration-gate-tied-to-tengu-melodic-ember","heading":"Prompt screening by mods is announced earlier, with a new gate on hook registration","tier":"soon","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/hook-registration-gate-tied-to-tengu-melodic-ember","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Prompt screening by mods is announced earlier, with a new gate on hook registration\n\nThe `prompts_screened_v1` capability is now announced as soon as a plugin loads, alongside a hook-registration check tied to `tengu_melodic_ember`\n\n**Unclear.** It is not stated what this check controls for users or which side of the switch is the new behaviour.\n\n**What**\n\nMods are plugins that can hook into Claude Code events. A mod hooked on `prompt.submit` can screen your prompts before they are sent. Several pieces changed around this:\n\n- Earlier announcement: a new optional `prompts_screened` field on an internal event announces the `prompts_screened_v1` capability as soon as a plugin loads or reloads, while a mod is hooked on `prompt.submit`. Before, this was only announced on the next `system\/init` message.\n\n- Hook-registration check: a new check passes only when a plugin-runtime check passes and the flag `tengu_melodic_ember` is off (its fallback is off). It replaces an older check. New code also adds the markers `prompts_screened_v1` and `ui_hooked_v1`, and, for the VS Code surface, a check that hook registration is not still owed or in progress. What the replaced check controls further on was not traced.\n\n- Schema field: a separate optional `expectSha256` field is added to a schema.\n\n`tengu_melodic_ember` is a gate, a remote switch that turns behaviour on or off. The flag server returned off for this site's account and for the anonymous baseline, and no reading has been taken under this release yet.\n\n**Why**\n\nPrograms built on the Claude Code SDK (the kit for running it from other software) learn sooner that prompt screening is active, instead of waiting for the next init message.\n\n- Flag `tengu_melodic_ember`: Off in both readings (read for one account on one subscription tier against v2.1.299; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Hooks\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}