Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.248 Home All releases olderv2.1.247 v2.1.250newer
Claude Code v2.1.248

Forwarding plugins and hooks to remote sessions is gated, and now says why it is off

Not switched on
Useful3 Signal4
Remote Control Notable

Forwarding your plugins and hooks into remote sessions stays off unless the server enables it.

Local plugin and hook forwarding into remote sessions is fully wired but sits behind two server flags that compile as false.

Feature flag
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.248: on

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.248: on

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

What

Sending your local plugins and hooks into a remote session is now controlled by a consistent set of checks, and when plugin forwarding does not happen the session records the reason rather than a bare failure flag. Both kinds of forwarding depend on two server-side feature flags that compile with a fallback of false, so in this build neither is on unless the server turns them on.

Details
  • Plugin forwarding reports one of three reasons: "switched off on this machine" when CLAUDE_CODE_DISABLE_PLUGIN_FORWARDING is set, "not enabled for this account" when the feature check fails, and "could not be sent from this machine" when setup throws.
  • Both plugin and hook forwarding require the two feature flags tengu_violin_wood and tengu_violin_amati, internal server-controlled toggles that each default to false, so without server-side values forwarding is off.
  • Hook forwarding adds two further conditions: the platform must not be Windows, and CLAUDE_CODE_DISABLE_HOOK_FORWARDING must not be set.
  • The hook checks were consolidated into a single helper called where the remote channel is created, replacing a different check that was there before.
Evidence

switched_off: "switched off on this machine", !a.CLAUDE_CODE_DISABLE_HOOK_FORWARDING

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

See this entry in the whole of v2.1.248 →