Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

Flag values can be pinned for the life of the process, and a new pinned flag appears

Some feature flags now stay fixed for the whole session, including a new one that is on.

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

Instead of one hand-written cache per flag, there is now a shared map that remembers the first value each flag returned and keeps it for the whole process, so a remote-config change mid-session cannot flip it. Three flags use it, including tengu_slate_anchor, new in this build and compiled on.

Details
  • Pinned flags: tengu_tab_read_sep (compiled off), tengu_tranquil_fern (compiled on) and tengu_slate_anchor (compiled on).
  • tengu_slate_anchor is read once inside the dynamic /loop tool's prompt, to ignore cache overage when working out the delay bounds shown to the model.
  • Compiled values are only the fallback; the live value comes from the server.
Evidence

tengu_slate_anchor

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Feature flag
tengu_slate_anchor Gate removed from the code

This release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.

This account: on · anonymous baseline: on · compiled default in v2.1.248: not a boolean we can read

tengu_tab_read_sep 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.248: not a boolean we can read

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

What has happened since
Flag reading moved The flag server now returns on for tengu_slate_anchor, read as this 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.
Flag reading moved The flag server now returns nothing at all, having stopped carrying it for tengu_slate_anchor, read as this 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.
Gate removed from the code v2.1.248 removed the tengu_slate_anchor gate from the code while it was still reading on for the account this site reads. The code path no longer asks a flag before it runs.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged /loop: self-paced dynamic mode and the no-prompt autonomous default are now always available, including on Bedrock/Vertex/Foundry

See this entry in the whole of v2.1.248 →

Feedback