Bot-free capture

Record both sides of a Mac meeting without a bot

A microphone alone misses the people coming through your speakers. A meeting bot changes the call. macOS process audio provides a third route.

Why ordinary recording falls short

Your microphone is designed to capture your voice, not clean digital output from Zoom, Teams, Meet, Slack, Webex, or FaceTime. Turning the speakers up and recording the room mixes both sides with echo, keyboard noise, and acoustic processing. A cloud meeting bot avoids that acoustic problem but becomes another participant, may require calendar access, and sends the call through an external service.

The two-track approach

LokalBot records two synchronized audio sources: the selected microphone and a Core Audio process tap for the selected meeting application's output. The transcript labels describe where the audio was captured, not a verified speaker identity. A shared microphone, headphones leaking into the mic, or meeting audio played into the room can put the same voice on either source.

When several voices occur in the system-audio source, optional on-device diarization can estimate additional speaker turns. Diarization is probabilistic, so identities and boundaries may still need editing after a difficult or overlapping conversation.

The Windows and Linux versions (alpha) also record two tracks. The second one is the meeting app alone where it can be separated: WASAPI process loopback on Windows build 20348 or later, and the app's own PulseAudio or PipeWire streams on Linux. Otherwise it is everything the computer plays, so notifications or music playing during the call end up in the recording too. Calendar matching there uses private iCal or CalDAV links instead of macOS Calendar. See the system requirements.

What the other participants see

No account joins the room, no virtual participant appears in the roster, and no bot announces itself. That makes the workflow less disruptive, but it does not make recording invisible in a legal or ethical sense. Tell people when required, obtain consent, and follow employer and platform policies. LokalBot is a personal recorder; it cannot decide whether a particular meeting may be recorded.

Permissions and controls

After the call

The selected local speech model transcribes the synchronized audio. The built-in language model can turn the transcript into a TL;DR, decisions, and action items. Because the capture sources are separate, you can replay the microphone and selected-app system audio independently and search from a result back to the relevant timestamp. Those sources still describe audio provenance rather than verified identity.

A pre-meeting test worth doing

Open the actual meeting app, play remote audio, speak into your microphone, and make a short recording. Verify that both tracks show activity and play back correctly. macOS permissions and device routing can change when you switch headsets, docks, or output devices, so repeat this check before an unusually important call.

FAQ

Questions about this guide

Does LokalBot join Zoom or Google Meet?

No. It records the selected app's audio locally through macOS rather than joining as a participant.

Can it identify every speaker?

No. It separates microphone audio from the selected app's output, and those sources do not prove identity. Optional diarization can estimate distinct voices within system audio, but accuracy depends on the recording.

Is bot-free recording legal everywhere?

No recording method is automatically legal everywhere. You are responsible for notice, consent, workplace rules, and local law.

Try it locally

Meeting notes that stay on your computer by default.

Free, open source, and no account. For Mac, with Windows and Linux in alpha.

Download for macOS

Apple Silicon · macOS 15+ · or with Homebrew: brew install --cask stevyhacker/tap/lokalbot

macOS · Windows · Linux (alpha) · requirements