Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.282 ·

Artifact republishing can save an exact copy of the latest version to work from

When republishing an artifact, Claude Code can now save an exact copy of the current HTML and tell Claude to build the next version from it

Under the hood Internal Changes
JSON All of v2.1.282
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.282,
Internal ChangesSection of the release
What

Claude Code has a check that runs before an artifact (a published page Claude builds for you) is published again. The check looks for whether the stored version has changed since Claude last saw it. It has changed in a few ways:

  • When the copy Claude is shown differs from the stored HTML, the exact HTML is now also saved to a file on disk, and Claude is told to base its next publish on that saved file.
  • The result now records where the latest version came from: Claude's own publish, a page save, another publish, or unknown.
  • When the starting version cannot be verified, the result now points to the file that has not been read.

The check only runs when a switch that is controlled remotely is turned on. Otherwise it does nothing.

Why

Building the next version from the exact latest copy makes it less likely that republishing an artifact drops content someone else published in the meantime.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich remote switch controls this check, and whether it is on by default, is not known.

See this entry in the whole of v2.1.282 →

Feedback