{"version":"2.1.261","anchor":"artifact-egress-blocked-message-distinguishes-remote-session","canonical_anchor":"artifact-egress-blocked-message-distinguishes-remote-session","heading":"Artifact egress-blocked message distinguishes remote sessions","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/artifact-egress-blocked-message-distinguishes-remote-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Artifact egress-blocked message distinguishes remote sessions\n\nBlocked artifact network requests now explain clearly when the restriction is due to running remotely.\n\nWhen a network allowlist blocks fetching an artifact's frame content, the error message now checks `CLAUDE_CODE_REMOTE`. On a remote session it tells the user that this is a restriction of where the session runs and that retrying locally won't help, instead of suggesting they add the domain to the environment's allowed domains.\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}