{"version":"2.1.292","anchor":"cloud-session-artifact-policy-403-gets-a-distinct-model-faci","canonical_anchor":"cloud-session-artifact-policy-403-gets-a-distinct-model-faci","heading":"Artifacts in cloud sessions give a clearer message when access is refused","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/cloud-session-artifact-policy-403-gets-a-distinct-model-faci","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Artifacts in cloud sessions give a clearer message when access is refused\n\nWhen a cloud session cannot confirm the organization's artifact settings, Claude is told not to retry and that it isn't a network problem\n\n**What**\n\nIn a cloud session, if Claude Code is refused (an HTTP 403 error) when it fetches the organization's settings for artifacts, Claude now gets its own instruction. It is told not to retry now, and to tell you that artifacts are unavailable because Anthropic couldn't confirm your organization's settings for this cloud session, and that it isn't a problem with your network. Before, only a general message was given, and only for one other kind of failure.\n\n**Why**\n\nClaude stops retrying a request that will not work and no longer suggests your network is at fault.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}