Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
Internal ChangesKind: in v2.1.282,
Internal ChangesSection of the release
Unclear Whether the artifact feature is available to every user is not known.
What
Artifacts are pages Claude publishes. When a publish is refused because a newer version exists, Claude Code now remembers where the refused content was handed over and any source file Claude had not read.
If Claude then sends exactly the same content again, it is refused with a new reason, identical_resubmission_confirmed, and told that sending it once more will go through. This happens when either of these is true:
Claude confirmed it viewed the live version after the refusal.
The live version reached Claude earlier in the same turn.
Before, every identical resend was refused with advice to merge changes and fetch the latest version again. New messages shown to you explain both situations, including one saying the artifact hasn't changed since, so publishing once more should go through.
Why
Claude could get stuck being refused over and over even after confirming its content matched the latest version. This gives it a way out of that loop.
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 doubtWhether the artifact feature is available to every user is not known.
