{"version":"2.1.232","anchor":"clearer-explanations-when-artifacts-are-unavailable","canonical_anchor":"clearer-explanations-when-artifacts-are-unavailable","heading":"Clearer explanations when artifacts are unavailable","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/clearer-explanations-when-artifacts-are-unavailable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Clearer explanations when artifacts are unavailable\n\nWhen artifacts are unavailable you now get a specific reason, including org policy or custom base URL.\n\n**What**\n\nTwo 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`.\n\n**Details**\n\n- The org-denied case reads \"Artifacts are disabled by your organization's policy. Contact your organization admin to enable them, then retry.\"\n\n**Evidence**\n\n`Artifacts are disabled by your organization's policy. Contact your organization admin to enable them, then retry.`\n\n- Area: Artifacts\n- Names: `ANTHROPIC_FEDERATION_RULE_ID`, `ANTHROPIC_ORGANIZATION_ID`, `ANTHROPIC_BASE_URL`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}