{"version":"2.1.239","anchor":"blocked-artifact-hosts-now-name-the-domain-to-allow","canonical_anchor":"blocked-artifact-hosts-now-name-the-domain-to-allow","heading":"Blocked artifact hosts now name the domain to allow","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/blocked-artifact-hosts-now-name-the-domain-to-allow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Blocked artifact hosts now name the domain to allow\n\nIf your network blocks artifact content, the message names the exact domain to allowlist.\n\n**What**\n\nWhen your environment's network allowlist denies the host that serves artifact content, the guidance now says the live version can be neither read nor handed over, and names the exact domain to add and where to add it.\n\n**Details**\n\n- The domain to allow is `*.frame.claudeusercontent.com`, added in environment settings, or in admin settings if the environment is shared.\n- Only appears when that host is in the session's denied-egress set.\n\n**Evidence**\n\n`*.frame.claudeusercontent.com`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}