handleAnswer hard-codes the join preferences: startCall(room, { microphone: true, video, sound: true }) where video = info.intent === 'video'. Every other join path honours the cameraOnJoin setting (default false, described in Settings as "Camera is off by default") and the persisted callPreferences, which deliberately never restores video "for privacy". Pressing Answer on an incoming video call therefore publishes the camera immediately with no prescreen, no preview and no respect for cameraOnJoin. The same line also forces microphone: true and sound: true, silently discarding a persisted muted/deafened preference (PTT is the only thing that overrides it, via forceAudioOff).
How to trigger
Settings → Calls → "Join with Camera On" = off (the default). Have someone place a video call to you in a DM. Press Answer — your camera goes live.
Suggested fix
build the answer preferences from the callPreferences atom + cameraOnJoin (video: cameraOnJoin && info.intent === 'video'), the same way PrescreenControls does, or route "Answer" through the prescreen.
Filed from the September 2026 client audit (branch lotus @ 4bea4895).
**Severity:** high · **Type:** bug · **Confidence:** high
**Location:** `src/app/components/CallEmbedProvider.tsx:567-574`, `src/app/state/callPreferences.ts:31-38`, `src/app/state/hooks/callPreferences.ts:26,61`, `src/app/features/settings/general/General.tsx:1569-1572`
### Problem
`handleAnswer` hard-codes the join preferences: `startCall(room, { microphone: true, video, sound: true })` where `video = info.intent === 'video'`. Every other join path honours the `cameraOnJoin` setting (default **false**, described in Settings as "Camera is off by default") and the persisted `callPreferences`, which deliberately never restores `video` "for privacy". Pressing **Answer** on an incoming video call therefore publishes the camera immediately with no prescreen, no preview and no respect for `cameraOnJoin`. The same line also forces `microphone: true` and `sound: true`, silently discarding a persisted muted/deafened preference (PTT is the only thing that overrides it, via `forceAudioOff`).
### How to trigger
Settings → Calls → "Join with Camera On" = off (the default). Have someone place a video call to you in a DM. Press Answer — your camera goes live.
### Suggested fix
build the answer preferences from the `callPreferences` atom + `cameraOnJoin` (`video: cameraOnJoin && info.intent === 'video'`), the same way `PrescreenControls` does, or route "Answer" through the prescreen.
---
_Filed from the September 2026 client audit (branch `lotus` @ 4bea4895)._
jared
added this to the Audit 2026-09 · High milestone 2026-09-12 01:50:47 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: high · Type: bug · Confidence: high
Location:
src/app/components/CallEmbedProvider.tsx:567-574,src/app/state/callPreferences.ts:31-38,src/app/state/hooks/callPreferences.ts:26,61,src/app/features/settings/general/General.tsx:1569-1572Problem
handleAnswerhard-codes the join preferences:startCall(room, { microphone: true, video, sound: true })wherevideo = info.intent === 'video'. Every other join path honours thecameraOnJoinsetting (default false, described in Settings as "Camera is off by default") and the persistedcallPreferences, which deliberately never restoresvideo"for privacy". Pressing Answer on an incoming video call therefore publishes the camera immediately with no prescreen, no preview and no respect forcameraOnJoin. The same line also forcesmicrophone: trueandsound: true, silently discarding a persisted muted/deafened preference (PTT is the only thing that overrides it, viaforceAudioOff).How to trigger
Settings → Calls → "Join with Camera On" = off (the default). Have someone place a video call to you in a DM. Press Answer — your camera goes live.
Suggested fix
build the answer preferences from the
callPreferencesatom +cameraOnJoin(video: cameraOnJoin && info.intent === 'video'), the same wayPrescreenControlsdoes, or route "Answer" through the prescreen.Filed from the September 2026 client audit (branch
lotus@4bea4895).