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.239entry #13

Claude Code v2.1.239 ·

Device hook forwarding worker added, off behind two flags and a kill switch

Cloud sessions could register hooks that run on your device, blocked by two off flags.

Nothing to try yet Notable No documentation found In Development
JSON All of v2.1.239
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
HooksArea: what it touches
In DevelopmentKind: in v2.1.239,
What probably matters to youSection of the release

Device hook forwarding is now implemented but needs two account flags that default off, and an env var refuses it.

What

The previous build had only the message shape for registering device hooks; this one adds the working half, letting a cloud session register hooks that run on your device. Nothing forwards in practice: it requires two account flags that both default to off, and setting CLAUDE_CODE_DISABLE_HOOK_FORWARDING refuses it outright.

Details
  • The SDK control loop now routes the register_device_hooks request to a worker holding a hook registry, lease handling and an admission check.
  • Admission requires an SDK URL, CLAUDE_CODE_REMOTE_SESSION_ID set, CLAUDE_CODE_ENVIRONMENT_KIND unset, an allowlisted entrypoint, non-hermetic mode, and the kill switch unset; otherwise the request is refused with a reason string.
  • Even when admitted the worker reads tengu_violin_amati and tengu_violin_wood and clears the registry unless both are on; both fall back to false on error.
  • Managed settings that restrict hooks to plugins, disable customization, allow managed hooks only, or disable all hooks also refuse it.
Evidence

hook_forwarding_disabled: flag_off

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundleCLAUDE_CODE_DISABLE_HOOK_FORWARDING
Feature flag
tengu_violin_amati 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.239: off

tengu_violin_wood 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.239: off

Read once, for one account on one subscription tier, against v2.1.239. 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_violin_amati, 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.
Flag reading moved The flag server now returns off for tengu_violin_amati, 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.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_violin_amati, 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
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_DISABLE_HOOK_FORWARDING

See this entry in the whole of v2.1.239 →

Feedback