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

Publish conflicts now say where the newer version came from

You'll notice
Useful3 Signal2
Artifacts

Publish conflicts now say whether the newer version came from the page, another session, or elsewhere.

What

When a publish is rejected because a newer version exists, the message states whether that version was saved from inside the page, published by another session, or of unknown origin, and explains that forcing would discard that specific version.

Details
  • A new fixed line tells the model that force is refused outright over a version saved from inside the page, and that only a publish built on that version will be accepted.
  • Applies on every publish, no flag involved.
Evidence

The server refuses force:true over a version saved from inside the page; only a publish built on that version is accepted.

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 →