Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

Replies are suppressed when another session already answered the summon

You'll notice
Useful3 Signal0
Artifacts

If another session already answered a comment, the duplicate reply is dropped instead of posted.

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.225 →