Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.247,
What probably matters to youSection of the release
tengu_cobalt_plinth_fennel is compiled off, read once, and its reader has no visible caller anywhere in the build.
What
A new artifact-relay flag, compiled to off, is read by a single small function whose name was freed up by renaming the route-classifying helper that used to own it. No call to that function appears in the surrounding module, and the flag name occurs exactly once in the whole build.
Details
Name reuse across scopes in this build means a caller elsewhere cannot be ruled out; either way the fallback is off, so whatever it selects needs a server-side value.
Live in the same module: the relay now reports once per session, under artifact_frame_relay / bot_context_not_served, that bot contexts are not relayed.
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
Flag reading movedThe 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 movedThe 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.
