Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Clearer explanations when artifacts are unavailable

You'll notice
Useful3 Signal3
Artifacts

When artifacts are unavailable you now get a specific reason, including org policy or custom base URL.

ANTHROPIC_FEDERATION_RULE_IDANTHROPIC_ORGANIZATION_IDANTHROPIC_BASE_URL
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.

See this entry in the whole of v2.1.232 →