Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.223 ·

Artifact comment replies can be applied as find/replace patches

Replies to artifact comments can be turned into find/replace edits, with one retry if an edit misses.

Nothing to try yet In Development
JSON All of v2.1.223
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
In DevelopmentKind: in v2.1.223,
What probably matters to youSection of the release

A patch applier with retry and failure reasons is built, reachable only via the artifact-comments autoreact feature whose gate is unresolved.

What

A new applier turns a model reply to an artifact comment into a list of find/replace edits against the artifact content, with a single retry when an edit does not land.

Details
  • Walks a list of {find, replace} edits and fails with a reason of "malformed", "not_found", "ambiguous" (the find text occurs twice) or "noop".
  • On the first not_found or ambiguous failure it re-prompts the model once, echoing the offending find text inside fenced DATA and telling it the text "occurs more than once at the point that edit applies (the source as modified by the preceding edits)".
  • Outcomes are reported as edit_patch_apply_failed, edit_patch_retry_fired, patch_retry_echo_refused and stopped_before_patch_retry.
  • Reachable only through the surrounding artifact-comments autoreact feature, whose gate could not be resolved in this build.
Evidence

occurs more than once at the point that edit applies (the source as modified by the preceding edits)

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.223 →

Feedback