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.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

Artifact data files need a known file type

Use it now
Useful3 Signal2
Artifacts

Publishing an artifact data file with an unknown extension fails early and tells you to set contentType.

contentTypefiles
What

Publishing a data file with an artifact by path now fails up front if the file's extension has no known content type, and the error tells you to rename it to something recognised or list it under files in map form with an explicit contentType.

Details
  • The error text suggests .json or .txt as known extensions.
  • Path resolution was reworked to try both the working directory and its real (symlink-resolved) path before computing the key the file is published under.
Evidence

has no known content type for its extension \u2014 rename it to a known one (e.g. .json or .txt)

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.246 →