Comment reading requires tengu_onyx_sluice, which falls back off and returns a "not available right now" message.
Reading comments on an Artifact is gated on tengu_onyx_sluice, which falls back to off in this build. With it off nothing is fetched at all and you get "comments are not available on this artifact right now", counted as cp_read_disabled. With it on, transport errors and HTTP 5xx or 499 are retried once after a random backoff and the unavailable message includes the HTTP status.
- Retries are reported as
server_read_retried. - The old path that fetched comment JSON directly from the content host is gone, along with its
__frame_tandjson_egress_blockedhandling.
cp_read_disabled
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_onyx_sluice Off by default, switched on for this accountThe 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.242: off
Read once, for one account on one subscription tier, against v2.1.242. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
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.