Claude Code v2.1.225 ·
Replies are suppressed when another session already answered the summon
If another session already answered a comment, the duplicate reply is dropped instead of posted.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
What
If a summon was already answered in another session, the drafted reply is discarded rather than posted, and the caller is told why.
Details
- New
summon_answered result path reports the reply was not posted and that the standing answer is already in the thread - The auto-react flow gained
answeredElsewhereNoticeText variants for cases where the artifact is published but the reply is withheld - Telemetry records
summon_answered_elsewhere
Evidence
Reply not posted: this summon was already answered in another session, and the standing answer is in the thread.
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 →
