An artifact must declare database capability when published, or database calls fail and ask you to republish.
Per-artifact database opt-in is gated behind CLAUDE_CODE_ARTIFACT_DB and its remote flag.
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.224: 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.224. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Among the new database errors for artifacts is one for publishing: if the artifact's currently published version does not declare the db capability, the call fails and tells you to republish with it declared. Database access is opt-in per artifact rather than automatically available. Gated by CLAUDE_CODE_ARTIFACT_DB and the tengu_umber_lattice flag.
this artifact's current published version does not declare the database capability \u2014 republish it with the db capability declared, then retry
Strings lifted out of the shipped bundle, so the claim above can be checked against them.