{"version":"2.1.251","anchor":"live-room-events-always-need-a-human-approval","canonical_anchor":"live-room-events-always-need-a-human-approval","heading":"Live room events always need a human approval","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/live-room-events-always-need-a-human-approval","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Live room events always need a human approval\n\nBroadcasting a live event to artifact viewers always asks you first, no exceptions.\n\n**What**\n\nThe `room_send` action, which broadcasts a live, non-persisted event to everyone currently viewing a published artifact, cannot be auto-approved under any configuration. It is refused in plan mode, refused in a Cowork session with no way to show an approval card, and otherwise raised as an ask prompt that no always-allow rule can satisfy.\n\n**Details**\n\n- Plan mode refusal reads \"Live room events cannot be sent from plan mode\".\n- Without a consent surface the Cowork refusal points you at the approval card.\n- The ask permission sets suppression of always-allow rules, and the automatic permission classifier is explicitly barred from approving it.\n- Inputs are validated: a lowercase topic name, and a JSON object payload under a size cap. Delivery and peer counts come back to the model as the tool result.\n\n**Evidence**\n\n`Live room events cannot be sent from plan mode`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}