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

A slow artifact publish can no longer leak into the next conversation

You'll notice
Useful3 Signal2
Artifacts

A slow artifact publish finishing after /clear no longer writes into your new conversation.

/clear
What

Publishing an artifact now records the account and conversation it started in, and the session state written after the server responds is only kept if both still match. A publish that finishes after /clear or an account switch no longer writes its slug, verification record or cached contract into the new session.

Details
  • The state guarded this way includes the registry of slugs published by this session, the last-publish record used for verification, and the cached publish contract pin.
  • Resetting a conversation without continuing it bumps the conversation counter and clears the published-slug registry.
  • Unconditional; both counters start at 0.
Evidence

ownPublishedSlugs

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 →