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.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Publishing re-checks the server for a comment room before skipping one

You'll notice
Useful2 Signal3
Artifacts

Publishing checks the server for comment-room support before skipping it.

What

When a published artifact does not locally look like it has a comment room but was created from a type with the room setting on, publish now asks the server for the artifact's capabilities before deciding, instead of trusting only local knowledge.

Details
  • If that read fails or comes back empty, the reported room status is the existing skip reason, or the new value unread when there is none.
  • Still inside the existing room consent and schema checks; no new flag.
Evidence

zt.artifactRoomSkipReason(ee) ?? "unread"

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