{"version":"2.1.239","anchor":"reading-someone-else-s-artifact-asks-you-once-then-remembers","canonical_anchor":"reading-someone-else-s-artifact-asks-you-once-then-remembers","heading":"Reading someone else's artifact asks you once, then remembers for the conversation","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/reading-someone-else-s-artifact-asks-you-once-then-remembers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Reading someone else's artifact asks you once, then remembers for the conversation\n\nReading someone else's published page now asks you once, then remembers for the rest of the conversation.\n\n**What**\n\nReading a published page now runs through its own permission branch instead of borrowing WebFetch's. Your own artifacts are read without a prompt; the first read of someone else's asks you, and that approval is remembered for the rest of the conversation.\n\n**Details**\n\n- A URL that is not a recognisable artifact link is rejected outright, with text telling the model to use a URL from the list or publish result.\n- Deny and ask rules written for `Artifact` or `WebFetch` are both consulted before the read runs.\n- In plan mode, reading another person's artifact is refused rather than prompting, since no one can answer.\n- The automatic permission classifier is never allowed to approve one of these reads on your behalf.\n\n**Evidence**\n\n`This is not an artifact url Claude can read. Use the artifact url from the list or publish result.`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}