When an artifact is published as a patch (only the changes, not the whole thing) and the publish is not forced, Claude Code now sends a set of preconditions for each file when the Artifact tool provides them. A precondition is a check that the file on the server is still the version it was based on. If the server refuses with a precondition_failed conflict, Claude Code now reads out which files conflicted. Its conflict telemetry records if_match_sent and conflict_paths.
If someone else changed the same files first, a patch publish can now be stopped instead of overwriting their work, and the conflict names the exact files involved. The related server-side flag tengu_cobalt_plinth_fern has read on both for this site's account and for an anonymous baseline, in readings not yet taken under this release.
tengu_cobalt_plinth_fern 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.281: 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.281. It isn't a statement about your account. What a flag value here can and cannot tell you