{"version":"2.1.232","anchor":"replies-stop-when-someone-else-s-claude-was-summoned-to-the-","canonical_anchor":"replies-stop-when-someone-else-s-claude-was-summoned-to-the-","heading":"Replies stop when someone else's Claude was summoned to the thread","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/replies-stop-when-someone-else-s-claude-was-summoned-to-the-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Replies stop when someone else's Claude was summoned to the thread\n\nIf someone else's Claude was summoned to a comment thread, your reply is dropped with a clear reason instead of retrying.\n\n**What**\n\nIf a comment thread was summoned or activated by a different person's Claude session, the reply is now refused with a specific outcome, and the model is told the draft was discarded and not to retry rather than being left to guess.\n\n**Details**\n\n- A 403 identifying a foreign sender maps to a `summon_foreign` outcome, which is also an optional field on the reply schema.\n- Telemetry gains `summon_foreign_sender`, `summon_foreign_notice_suppressed` and `edit_reply_summon_foreign`.\n- Part of the artifact comments feature, which is itself behind remote-config gates, so whether you see it depends on server configuration.\n\n**Evidence**\n\n`summon_foreign_sender`, `reply not posted (another user's summon or activation)`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}