Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.317,
Internal ChangesSection of the release
Unclear It is not stated what this allow-list controls, or whether anything a reader can reach uses the route yet.
What
Claude Code keeps a list of web routes it allows. A route is a kind of request paired with an address, such as a request to fetch (GET) a path. GET /artifacts now appears on that list. It sits in its own group, separate from the /deploy and /upload routes.
Why
Fetching from /artifacts is handled as its own case rather than grouped with deploying or uploading.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not stated what this allow-list controls, or whether anything a reader can reach uses the route yet.
Anthropic's release notes agreeFixed /artifacts and the Artifact tool's shared list showing no shared artifacts when you have 200 or more of your own
