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.247entry #230

Claude Code v2.1.247 ·

Artifact relay skips bot-driven sessions

Bot-driven sessions no longer relay artifact requests; they go direct or not at all.

Under the hood In Development
JSON All of v2.1.247
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.247,
In DevelopmentSection of the release
What

When the session is a bot context, the code that decides how to reach the artifact service stops before relaying: it records bot_context_not_served once and returns either not-served or direct instead.

Details
  • The helper that picks the relay leg now takes a mode of "fallback", "bound" or "only" in place of a boolean.
  • A separate new predicate combines hosted session, bot context and the new flag tengu_cobalt_plinth_fennel, whose compiled fallback is off. The neighbouring relay flags tengu_cobalt_plinth_sorrel and tengu_cobalt_plinth_madder fall back to on.
  • The old boolean-argument helper was renamed and kept.
Evidence

bot_context_not_served

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

Read from
Feature flag
tengu_cobalt_plinth_fennel 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.247: not a boolean we can read

tengu_cobalt_plinth_sorrel On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

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

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

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

See this entry in the whole of v2.1.247 →

Feedback