Skip to content

Auto-record meetings starts on any browser mic use, and the menu bar stays idle while it records #345

Open

Description

@rajgharat07

What happened?

I turned on Auto-record meetings figuring it would catch Zoom/Meet-style calls. What it actually does is treat any Chrome/Safari/Firefox process holding the mic as a “meeting” — voice search, a getUserMedia test page, a site’s mic permission prompt, whatever. The code even says that out loud in MeetingAutoRecord.swift: a tab can’t be told apart from outside, so any browser mic counts, including non-call use.

When it fires, SystemAudioRecorder grabs the mic plus everything the Mac is playing, streams it to the realtime socket, and drops an .m4a under Application Support. That’s fine for a real call. It’s a lot less fine when I only opened voice search and Blurt’s menu bar still shows idle (MenuBarStatus only tracks dictation phases, not TranscriptsModel recording). Auto-start also never calls surfaceMainWindow(), so if the main window is closed there’s nothing obvious telling me capture started.

Settings footer says “browser call.” The trigger is broader than that. SECURITY.md still reads like audio only happens during dictation; this path is explicitly not the dictation capture.

Steps:

  1. Settings → General → turn on Auto-record meetings.
  2. Close / leave Blurt’s main window. Menu bar idle.
  3. In Chrome, open any page that takes the mic that isn’t a meeting (voice search or a simple getUserMedia demo) and keep the mic for ~5 seconds (probe interval).
  4. Watch Application Support Recordings / a proxy for streaming.assemblyai.com. Menu bar still idle.

Expected: only real conferencing / clear call contexts, or at least a menu-bar / window signal when auto-record starts, and docs that match the behavior.

Actual: any browser mic can start a full system-audio recording with almost no chrome, while SECURITY.md still sounds dictation-only.

Pointers if useful:

  • Sources/BlurtEngine/Pipeline/MeetingAutoRecord.swift (browserBundleIDs + comment)
  • App/Blurt/Blurt/Wizard/TranscriptsModel+Meetings.swift (startRecording(byUser: false), no surfaceMainWindow)
  • Sources/BlurtEngine/Audio/SystemAudioRecorder.swift
  • Sources/BlurtEngine/Pipeline/MenuBarStatus.swift
  • MeetingAutoRecordSection.swift footer (“browser call”)

I’d either narrow .browser starts or rename the setting and surface recording on the menu bar when auto-record is running. Not the same bug as #340 (teardown / pinned mic) or #338 (quit corrupting m4a/history).

macOS and Blurt versions

macOS 15+ · Blurt built from main

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions