{"version":"2.1.238","anchor":"blocked-artifact-asset-downloads-now-name-the-host-to-allow","canonical_anchor":"blocked-artifact-asset-downloads-now-name-the-host-to-allow","heading":"Blocked artifact asset downloads now name the host to allow","tier":"use","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/blocked-artifact-asset-downloads-now-name-the-host-to-allow","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Blocked artifact asset downloads now name the host to allow\n\nBlocked artifact downloads now tell you to allow `*.frame.claudeusercontent.com` in your network settings.\n\n**What**\n\nWhen fetching an image or file attached to an artifact is blocked by network egress rules, the error now says which frame host was refused and tells you to allow `*.frame.claudeusercontent.com` (and its staging variant) in your sandbox or desktop app network settings.\n\n**Details**\n\n- Three distinct failures are reported: blocked by egress policy, denied, and refused by the proxy.\n- The message makes clear that access to the artifact itself is unaffected.\n\n**Evidence**\n\n`so the asset cannot be fetched (access to the artifact itself is fine)`\n\n- Area: Artifacts\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}