Permissions

MeetGist needs two macOS permissions:

1. Microphone — to record your own voice.
2. Screen Recording — required by ScreenCaptureKit to capture system audio (the other side of the call) and to read the meeting window title for auto-naming.

The native app asks for both the first time you record. Click Allow for the microphone and enable MeetGist in the Screen Recording panel macOS opens. You’ll find both later under System Settings → Privacy & Security → Microphone and → Screen Recording, listed as MeetGist.

After you enable Screen Recording the first time, macOS asks you to quit and reopen MeetGist — that’s normal. Do it once and the grant sticks.

Note

Grants are tied to the app’s code signature. The app installed via make install-app uses a stable signature, so your permissions persist across rebuilds. A plain Xcode/ad-hoc build changes identity each time and would keep re-appearing as a new, ungranted app — which is why MeetGist installs to /Applications with a fixed identity.

Fail-fast check

A few seconds after you start, MeetGist confirms system audio is actually flowing. If Screen Recording is missing it stops immediately with a notification instead of recording a silent file for the whole meeting. A silent microphone only warns (it’s normal for a listen-only call), so system audio keeps recording.