The artifact database is behind CLAUDE_CODE_ARTIFACT_DB or a gate that falls back to false.
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.
tengu_umber_lattice 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.228: off
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
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.