{"version":"2.1.246","anchor":"new-flag-can-widen-when-the-extended-usage-limit-header-is-s","canonical_anchor":"new-flag-can-widen-when-the-extended-usage-limit-header-is-s","heading":"New flag can widen when the extended usage-limit header is sent","tier":"soon","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/new-flag-can-widen-when-the-extended-usage-limit-header-is-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### New flag can widen when the extended usage-limit header is sent\n\nA server flag can widen when subagent requests send the extended usage-limit header.\n\n**What**\n\nThe 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.\n\n**Details**\n\n- `tengu_smooth_harbor` falls back to off, and is still combined with `tengu_lantern_spool`, which also falls back to off.\n- Nothing in the build turns either on, so absent remote config the behaviour is exactly what it was.\n\n**Evidence**\n\n`tengu_smooth_harbor`\n\n- Flag `tengu_smooth_harbor`: Not enough to say (read for one account on one subscription tier against v2.1.246; this account: no value returned, anonymous baseline: no value returned, compiled default: off)\n- Flag `tengu_lantern_spool`: Off in both readings (read for one account on one subscription tier against v2.1.246; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Elsewhere\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}