{"version":"2.1.232","anchor":"a-summon-relayed-from-another-user-s-edit-grant-now-fails-qu","canonical_anchor":"a-summon-relayed-from-another-user-s-edit-grant-now-fails-qu","heading":"A summon relayed from another user's edit grant now fails quietly","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/a-summon-relayed-from-another-user-s-edit-grant-now-fails-qu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### A summon relayed from another user's edit grant now fails quietly\n\nA summon relayed from another user's edit grant now fails quietly instead of commenting back.\n\n**What**\n\nWhen an artifact publish is denied because the edit grant was authored or granted by a different user, Claude Code stops and reports the refusal instead of posting an explanatory comment back onto the artifact thread.\n\n**Details**\n\n- The denial prefix is now a shared constant `publish denied: `, and the failure classifier strips it and matches remainders beginning \"this edit grant was authored by another user\" or \"this edit grant was granted by another user\".\n- Those cases classify as a foreign summon and return a publish-refused outcome immediately, skipping the reply composition step.\n- The artifact commenting feature has its own activation checks around this path.\n\n**Evidence**\n\n`this edit grant was granted by another user`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}