If another session already answered an artifact summon, yours says so instead of duplicating the reply.
What's wrong with this entry?
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.
- A 409 whose body reason is
summon_already_answered, or a response withsummon_answered: !0, maps to the outcome{ kind: "summon_answered" }. - The tool passes
answersSummonwith the reply, and the autoreact path threads a newdeclareAnswersSummonflag 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
answeredElsewhereNoticeTextnotice, for example that the follow-up note was withheld because another session's reply already stands in the thread. - Telemetry records
summon_answered_elsewhere.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.