Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.239 Home All releases olderv2.1.238 v2.1.240newer
Claude Code v2.1.239

Missing published files get their own 404 message

You'll notice
Useful2 Signal1
Artifacts

Asking for a missing file from a published artifact now returns its own 404 message.

What

Asking for a specific file from a published artifact and getting nothing back no longer shows the generic "no such file" text. It reports its own message and returns a 404 to the caller.

Details
  • The message covers both causes: no file is published at that path in the served version, or artifact reads through the session gateway are not enabled for the session.
  • Reported internally as an asset_file_not_found outcome.
Evidence

no file is published at that path in the served version — or artifact reads through the session gateway are not enabled for this session

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.239 →