Artifact comments could be fetched server-side instead of through the frame host, but that switch is off.
The server-side comment path sits behind tengu_onyx_sluice, default off, with fallback to the existing flow.
tengu_onyx_sluice 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.228: 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.228. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Fetching comments on an artifact can go through a new server-side path, falling back to the existing frame-host URL flow if the server call errors. The switch is tengu_onyx_sluice and its built-in default is off, so unless a remote configuration value turns it on, nothing changes for you.
- A fallback after a failed server call is recorded as
server_primary_fell_back.
server_primary_fell_back
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.