Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.299entry #327

Claude Code v2.1.299 ·

Prompt screening by mods is announced earlier, with a new gate on hook registration

The prompts_screened_v1 capability is now announced as soon as a plugin loads, alongside a hook-registration check tied to tengu_melodic_ember

Group of 2 Nothing to try yet In Development
JSON All of v2.1.299
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
In DevelopmentKind: in v2.1.299,
In DevelopmentSection of the release

Unclear It is not stated what this check controls for users or which side of the switch is the new behaviour.

What

Mods 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:

  • 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.
  • 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.
  • Schema field: a separate optional expectSha256 field is added to a schema.

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.

Why

Programs 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.

Read from
Feature flag
tengu_melodic_ember Off in both readings

The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.

This account: off · anonymous baseline: off · compiled default in v2.1.299: 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.

Read once, for one account on one subscription tier, against v2.1.299. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_melodic_ember, read as this account. A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.

See this across every release →

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not stated what this check controls for users or which side of the switch is the new behaviour.
The name it cites is new in this buildNew in this build: tengu_melodic_ember

See this entry in the whole of v2.1.299 →

Feedback