Artifact auto-reply appears only with comments enabled, and an embeds field is compiled out entirely.
auto_reply needs CLAUDE_CODE_ARTIFACT_COMMENTS or a remote flag defaulting off; embeds sits behind a false build constant.
tengu_teal_corbel On for this account, and not off by defaultThe 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.239: on
Read once, for one account on one subscription tier, against v2.1.239. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
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.
auto_reply
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Artifact auto-reply subscriptions can be stopped from the cancel gestures
Both mention comment
-
v2.1.221
New artifact comment threads: read, reply, resolve
Both mention comment
-
v2.1.235
Artifact MCP is on by default
Both mention comment