Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.268 ·

Artifact read permission check for WebFetch now runs a deny check both before and after network egress probing

WebFetch's permission check for reading claude.ai artifacts now re-checks deny rules after probing network access

TierYou'll noticehow much it should matter to you
Useful1my rating, 1 to 5
Signal1worth watching, 1 to 5
AreaArtifactswhat it touches
KindBug Fixesin v2.1.268,
You'll notice

WebFetch's permission check for reading claude.ai artifacts now re-checks deny rules after probing network access

What

When WebFetch is used to read a claude.ai artifact, Claude Code now runs its deny-rule permission check a second time, after the step that probes network access and shows any consent surface, in addition to the check that already ran earlier. Only after this second check passes does the flow move on to handling ask rules.

Why

Running the deny check again after the network probe closes a gap where a deny rule might otherwise be missed if conditions changed between the first check and the actual network access.

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged plain WebFetch deny and ask rules to no longer apply to Artifact tool reads and updates; use an Artifact rule (or…

See this entry in the whole of v2.1.268 →

Feedback