/record start: a refusal can be public, and a refused start leaves the session live #843

New issue

Closed

opened 2026-09-26 14:49:05 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-09-26 14:49:05 +00:00

Collaborator

Follow-ups from #839's fix.

A refusal can be public. record_start defers the interaction publicly (interaction.response.defer()). The first followup after a public defer inherits that visibility, so ephemeral=True on the refusal is likely ignored. The existing refusals share this: SESSION_NOT_FOUND and the backend's 409.
- The fix: an ephemeral defer, plus a normal channel.send for the public announcement.
A refused start leaves the session live (D116). On the Discord path the bot calls POST /api/bot/sessions/{id}/recording-started (D10, D123 and D116 check and flip) before it connects. If the join or the announcement then fails, the session stays in_progress with no recording. The web path is fine, because D116 applies there only after the bot's 200.
- The fix: split the check from the flip, additively. Use a check-only call first, and flip after the announcement succeeds; or undo the flip on a refusal.

The bot contract must stay additive.

Refs #839, #731, #736.

Follow-ups from #839's fix. 1. **A refusal can be public.** `record_start` defers the interaction publicly (`interaction.response.defer()`). The first followup after a public defer inherits that visibility, so `ephemeral=True` on the refusal is likely ignored. The existing refusals share this: `SESSION_NOT_FOUND` and the backend's 409. - **The fix:** an ephemeral defer, plus a normal `channel.send` for the public announcement. 2. **A refused start leaves the session live (D116).** On the Discord path the bot calls `POST /api/bot/sessions/{id}/recording-started` (D10, D123 and D116 check and flip) before it connects. If the join or the announcement then fails, the session stays `in_progress` with no recording. The web path is fine, because D116 applies there only after the bot's 200. - **The fix:** split the check from the flip, additively. Use a check-only call first, and flip after the announcement succeeds; or undo the flip on a refusal. The bot contract must stay additive. Refs #839, #731, #736.

claude-bot referenced this issue

2026-09-26 16:58:41 +00:00

A web-started recording can run with no announcement (consent model) #839