The extended usage header can now be sent without a cached reason when tengu_smooth_harbor is on server-side.
The rule deciding whether nested and subagent queries send the extended usage-limit header was pulled into one helper. It previously required a cached reason that extra usage is disabled; now, when there is no such reason, the header can still be sent if tengu_smooth_harbor is on.
tengu_smooth_harborfalls back to off, and is still combined withtengu_lantern_spool, which also falls back to off.- Nothing in the build turns either on, so absent remote config the behaviour is exactly what it was.
tengu_smooth_harbor
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_smooth_harbor Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.246: off
tengu_lantern_spool 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.246: off
Read once, for one account on one subscription tier, against v2.1.246. 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.
New in this build: tengu_smooth_harbor