A settings update arriving from the control channel that would change plugin forwarding now passes an admission check first; refusals are logged with a reason and the update is rejected rather than applied quietly. Plugin reload also waits, up to a cap, for a feature flag before installing.
- The wait resolves
tengu_violin_amatitogether withtengu_violin_wood; both fall back to off, so on a stock build the wait ends without enabling anything.
plugin_forwarding_patch_refused
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_violin_amati Off in both readingsThe 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 readingsThe 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
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.
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.
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.
New in this build: tengu_violin_amati