{"version":"2.1.292","anchor":"artifacts-unavailable-message-for-403-on-cloud-sessions","canonical_anchor":"artifacts-unavailable-message-for-403-on-cloud-sessions","heading":"Clearer message when artifacts are blocked in a cloud session","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/artifacts-unavailable-message-for-403-on-cloud-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Clearer message when artifacts are blocked in a cloud session\n\nCloud sessions now explain that artifacts are unavailable because Anthropic couldn't confirm the organization's settings, not because of your network\n\n**What**\n\nIn a cloud session, artifacts can be blocked because Anthropic could not confirm your organization's settings. When that happens with an HTTP 403 error, Claude Code now shows a specific message and says the problem is not your network. HTTP 403 is the web's \"not permitted\" response. Before, this case showed a generic message.\n\nA new hint also tells you to choose the artifacts entry under the prompt once the session has an artifact.\n\n**Why**\n\nYou are not sent looking for a network problem that is not there.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}