Skip to content

v0.28.2: Live captures both sides of calls

Latest

Choose a tag to compare

@silverstein silverstein released this 08 Oct 19:58

Minutes 0.28.2 makes Live capture both sides of a call. Before this release, Go Live listened to one microphone only. On a call through headphones the other person never reached that microphone, so the live transcript and the saved meeting held only your side, with no warning (#1110).

What changed:

  • Go Live records your microphone and this Mac's audio whenever native call capture is available, with the live transcript on. It works whether or not Minutes has detected the call, so apps the detector does not know about are covered too.
  • A Live session started another way switches automatically. If Live was started from the hotkey or minutes live and a call begins, Minutes moves to both-sides capture on its own. If it cannot (for example, Screen Recording permission is off), the Live bar says so and why.
  • Starting Live no longer hides a detected call. A change in April cleared the call banner the moment Live or dictation started, which removed the one path that recorded the other side. Detected calls now stay detected, and the banner clears when the call actually ends.
  • Handing off from minutes live to a call recording no longer fails with "already owns capture" while the Live session finishes saving.
  • Live now logs which input device it used, so a missing-audio report can be diagnosed from the log.

Verified on macOS with AirPods as both input and output and a Google Meet call: microphone-only Live missed the other side, while Go Live during a call, Go Live before a call, and an automatic switch from minutes live all captured it.

Install or update:

  • macOS desktop: download the DMG below, or run brew update followed by brew upgrade --cask silverstein/tap/minutes.
  • Command line: cargo install minutes-cli --version 0.28.2.
  • MCP server: npx minutes-mcp@0.28.2 with the updated local Minutes engine.

Minutes remains free and open source. Your meeting files stay local; content you ask a connected cloud assistant to retrieve becomes context for that assistant under its settings.