Reading or writing a public artifact from outside your current organization is now blocked unless a person has approved it
What
- A new "public_unasked" reason code and reject path deny reading a public artifact from outside a user's organization unless a person has approved it, meaning no fetch happens at all without approval; a separate "tokenless" public-read path is gated the same way.
- A new deny check fires whenever an artifact's
outsideOrgReaderflag is set: any read or write against a public artifact from outside the user's current organization is denied outright, with a message explaining that nothing in the session can reach it. - New helpers read a cached, account/organization-scoped "artifact roster" to track approvals, and a dedicated message supplies the refusal text shown when fetching a public artifact from outside the user's organization and nobody has approved it.
Why
This stops artifacts belonging to other organizations from being silently read or modified, requiring explicit human approval first.
tengu_cobalt_plinth_sedge 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.274: 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.274. 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.
Whether this behavior is active for any given account depends on the `tengu_cobalt_plinth_sedge` setting, which no reading has yet confirmed…