Publishing an artifact can carry a template choice, switched off here, plus new edit attribution.
Artifact publishing can attach a template, picking "workshop" automatically, but the gate defaults off.
tengu_amber_quill_moth 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.221: on
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.221. 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 publish payload gained an optional template field that is only sent when the gate is on.
- Gated on
tengu_amber_quill_moth, in-source fallback false, so this is off in this build unless remote config turns it on. - When enabled and no explicit template was given, the publish path picks
"workshop"if a workshop surface is detected. - Separately and ungated: a new
auto_edit_attributionfield (thread_id / comment_id) is sent whenever present, and forces a base-version check the same way composed PR review does.
tengu_amber_quill_moth
Strings lifted out of the shipped bundle, so the claim above can be checked against them.