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.232 ·

Two feature decisions moved onto the shared process config object

The memory prompt variant and the skill-suggestion rollout are now fields on the process config.

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

Whether the "stone shell" memory prompt is served and whether the skill and plugin suggestion rollout is on are now fields on the per-process config object rather than loose module variables. Behaviour is unchanged.

Details
  • Both default to off: the suggestion rollout is decided by tengu_saddle_lantern, the memory prompt by tengu_stone_shell.
  • The suggestion accessor still declines to latch a value whose source is a fallback, so it can be re-evaluated later.
Evidence

return ((e.suggestRolloutEnabled ??= wBf().value), e.suggestRolloutEnabled);

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

Read from
Feature flag
tengu_saddle_lantern 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.232: 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.

tengu_stone_shell 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.232: off

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.232. 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_saddle_lantern, 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 off for tengu_saddle_lantern, 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 on for tengu_saddle_lantern, 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_saddle_lantern, 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_saddle_lantern 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.
Gate removed from the code v2.1.232 removed the tengu_saddle_lantern 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 →

See this entry in the whole of v2.1.232 →

Feedback