You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.232,
ImprovementsSection of the release
What
Two new sets of messages say why artifacts are off. One covers sessions whose API access comes from managed settings or the ANTHROPIC_FEDERATION_RULE_ID / ANTHROPIC_ORGANIZATION_ID environment variables. The other covers five specific causes: unverifiable org policy, unreadable plan, org denial, cache miss, and unavailable policy, the last pointing at session configuration such as a custom ANTHROPIC_BASE_URL.
Details
The org-denied case reads "Artifacts are disabled by your organization's policy. Contact your organization admin to enable them, then retry."
Evidence
Artifacts are disabled by your organization's policy. Contact your organization admin to enable them, then retry.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up ANTHROPIC_BASE_URL, on Claude Code changelog.* Fixed every turn failing with HTTP 400 on third-party Anthropic-compatible endpoints (`ANTHROPIC_BASE_URL`) since 2.1.265: a regex in the Artifact tool's input schema that those endpoints rejectchangelogsee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up ANTHROPIC_BASE_URL, on Claude Code changelog.
