You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.257,
ImprovementsSection of the release
WebFetch's permission check now dynamically loads a helper to decide whether an artifact fetch needs extra scrutiny before its content is allowed into the conversation. When enabled, it warms or reads the artifact's "share entry" to determine ownership: if the artifact belongs to another user, or ownership can't be confirmed, the request is forced to an ask decision with localDisplayOnly: true; if it belongs to another org, the request is denied outright.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added sinceA small documentation edit on Environment variables touched a line naming WebFetch after this was published.| `CLAUDE_CODE_WEBFETCH_DEADLINE_MS` | Upper bound in milliseconds on how long [WebFetch](/docs/en/tools-reference#webfetch-tool-behavior) waits for a page to download, including any redirects it follows. A download that hasn't completed b…env-varssee the edit
Confirmed sinceAnthropic's documentation has since written up WebFetch, on Archive Session.- `BetaManagedAgentsWebFetchToolConfig object`api/beta/sessions/archivesee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up WebFetch, on Archive Session.