Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.239,
What probably matters to youSection of the release
auto_reply needs CLAUDE_CODE_ARTIFACT_COMMENTS or a remote flag defaulting off; embeds sits behind a false build constant.
What
The auto_reply field of the artifact request schema now appears only when artifact comments are enabled, via the CLAUDE_CODE_ARTIFACT_COMMENTS environment variable or, failing that, the remote flag tengu_teal_corbel whose fallback is off. A separate embeds field sits behind a build-time constant set to false, so it never appears in the shipped schema.
Evidence
auto_reply
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_teal_corbelOff 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.239: off
Flag reading movedThe flag server now returns on for tengu_teal_corbel, 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_teal_corbel, 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.
