A rejected artifact credential now reports a distinct "report this" outcome rather than a permission answer.
The artifact database is behind CLAUDE_CODE_ARTIFACT_DB or a gate that falls back to false.
tengu_umber_lattice Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · 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?
A 403 with a recognised body from the artifact database now produces a distinct outcome, credential_rejected with reason custody_403, classified as unavailable. Its explanation states this is a client/server integration fault to be reported, not an answer about whether the artifact exists or whether you may see it. The artifact database itself is behind the CLAUDE_CODE_ARTIFACT_DB environment variable or the tengu_umber_lattice gate, whose fallback is false.
the server refused this session's credential at the artifact-db door, credential_rejected
Strings lifted out of the shipped bundle, so the claim above can be checked against them.