Source Intelligence
Follow Discord

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

Reading published files from a cloud session now reports why a read was refused

You'll notice
Useful2 Signal3
Artifacts

Failed reads of published cloud files now say whether the credential, the artifact, or a missing relay was the problem.

What

Listing and reading files from a published artifact go through the session gateway relay only, and failures now say which kind they are: a credential the gateway would not accept, an artifact the relay refused, or a session with no relay at all, which cannot retry the read locally.

Details
  • The relay-only path also turns off the public-read fallback.
  • A 403 or 404 from the relay is reported as a refusal; a 401 is the new unauthorized case, which did not exist in v2.1.238.
Evidence

the session gateway did not accept this session's credential for the artifact relay; retrying from here will not help

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.239 →