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
HomeReleasesv2.1.236entry #156

Claude Code v2.1.236 ·

Early artifact comment read is behind two flags, both off

The early artifact comment read needs two separate switches, both of which default off.

Nothing to try yet In Development
JSON All of v2.1.236
Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.236,
In DevelopmentSection of the release

The auto-reply scan passes the early-read option only under tengu_slate_lantern_ember, and the read itself needs tengu_onyx_sluice.

What

The pre-startup control-plane comment read has one caller, the artifact comment auto-reply scan, and it passes the option only when tengu_slate_lantern_ember is on. Even then the read itself needs tengu_onyx_sluice. Both fall back to off, so neither half runs unless remote config enables both.

Details
  • The option defaults to false at the reader itself, and no other code in the build passes it.
  • The attempt carries a callback so it is scored whether it succeeds or falls back to the normal read.
  • The same change lets a session whose outbound network is blocked reuse an already-successful control-plane result rather than reporting a denial.
Evidence

controlPlaneReadBeforeBoot

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

Read from
Feature flag
tengu_slate_lantern_ember 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.236: off

tengu_onyx_sluice Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: on · compiled default in v2.1.236: off

Read once, for one account on one subscription tier, against v2.1.236. 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_onyx_sluice, 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_onyx_sluice, 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.

See this across every release →

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_slate_lantern_ember

See this entry in the whole of v2.1.236 →

Feedback