Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.225entry #42

Claude Code v2.1.225 ·

Artifact replies detect that another session already answered the summon

If another session already answered an artifact summon, yours says so instead of duplicating the reply.

You'll notice New Features
JSON All of v2.1.225
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
New FeaturesKind: in v2.1.225,
New FeaturesSection of the release
What

Posting a reply to an artifact summon can now come back as "already answered elsewhere", so a second session does not duplicate a standing answer or retry pointlessly.

Details
  • A 409 whose body reason is summon_already_answered, or a response with summon_answered: !0, maps to the outcome { kind: "summon_answered" }.
  • The tool passes answersSummon with the reply, and the autoreact path threads a new declareAnswersSummon flag through reply and edit calls.
  • The tool returns replied:false with a result carrying summon_answered, and the model is told not to retry but to read the comments for the answer that landed.
  • The tool-use line shows "reply not posted (summon already answered)" instead of the generic reply-needs-thread-activation text.
  • The autoreact pipeline takes a separate answeredElsewhereNoticeText notice, for example that the follow-up note was withheld because another session's reply already stands in the thread.
  • Telemetry records summon_answered_elsewhere.
Evidence

summon_answered_elsewhere, Reply not posted: this summon was already answered in another session, and the standing answer is in the thread. The draft was discarded. Do not retry \u2014 read the comments to see the answer that landed., reply not posted (summon already answered), summon_already_answered

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

Feedback