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 no longer refuses when the model already saw the current version

You'll notice
Useful3 Signal2
Artifacts

Publishing no longer fails on a stale version when the model already saw the live one.

What

The guard that blocks a publish based on a stale document version can now let the publish through. If the model already observed the live version, the publish adopts that version as its base rather than failing with a "publish again in your next turn" style refusal.

Details
  • The guard result gained a proceedWith field carrying the live version, returned with no refusal text plus a replay record.
  • Telemetry labels this path proceed_own_version, distinguishing it from the seeded-refusal path.
  • The proceed branch also depends on two further checks in the same condition whose meaning is not resolved in this build.
Evidence

mode: c("proceed_own_version")

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 →