Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.280 ·

SESSION_PINNED (tengu_gentle_frost) gated behind an extra environment check

One of the SESSION_PINNED feature checks now requires an extra environment condition before it queries the flag server

Under the hood Internal Changes
JSON All of v2.1.280
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
InternalsArea: what it touches
Internal ChangesKind: in v2.1.280,
Internal ChangesSection of the release
What

SESSION_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.

Why

This 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.

Read from
Feature flag
tengu_gentle_frost 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.280: 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.

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

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_gentle_frost

See this entry in the whole of v2.1.280 →

Feedback