Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.247 Home All releases olderv2.1.246 v2.1.248newer
Claude Code v2.1.247

Artifact relay skips bot-driven sessions

Under the hood
Useful1 Signal2
Artifacts

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

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

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.

See this entry in the whole of v2.1.247 →