{"version":"2.1.280","anchor":"session-pinned-tengu-gentle-frost-gated-behind-an-extra-en","canonical_anchor":"session-pinned-tengu-gentle-frost-gated-behind-an-extra-en","heading":"SESSION_PINNED (tengu_gentle_frost) gated behind an extra environment check","tier":"internal","area":"Internals","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/session-pinned-tengu-gentle-frost-gated-behind-an-extra-en","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### SESSION_PINNED (tengu_gentle_frost) gated behind an extra environment check\n\nOne of the SESSION_PINNED feature checks now requires an extra environment condition before it queries the flag server\n\n**What**\n\nSESSION_PINNED is checked via two feature-flag lookups. One of them, tied to the `tengu_gentle_frost` flag, now first runs an additional environment check (`le()`) before it queries the remote feature-flag server at all, whereas previously it queried the flag unconditionally.\n\n**Why**\n\nThis narrows when Claude Code even bothers asking the flag server about this particular `tengu_gentle_frost` variant, likely to skip the remote check in environments where it wouldn't apply anyway.\n\n- Flag `tengu_gentle_frost`: Off in both readings (read for one account on one subscription tier against v2.1.280; this account: off, anonymous baseline: off, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}