Skip to content
MeetGist

Installation

MeetGist requires an Apple-Silicon Mac on macOS 14+.

MeetGist is free and open source, and not yet distributed as a notarized download — so you build it from source. It’s two commands.

Build & install

Prerequisites: Xcode (the full app, not just the Command Line Tools) and XcodeGen — brew install xcodegen.

Terminal window
git clone https://github.com/MeetGist/meetgist.git
cd meetgist
make install-app   # build, sign, and install /Applications/MeetGist.app
open /Applications/MeetGist.app

make install-app builds a Release app, signs it with a stable local identity (created once, automatically), and copies it to /Applications. That stable signature is what lets macOS remember your Microphone and Screen-Recording grants across rebuilds — a plain ad-hoc Xcode build changes identity every time and would keep re-asking and re-appearing as a “new” app. Always launch from /Applications, not from Xcode.

Because the build is self-signed (not notarized), the first launch may show an “unidentified developer” notice — right-click the app and choose Open once.

The app is fully native — everything runs inside it, no Python or terminal needed.

Prefer the terminal? The script edition

The same engine also ships as a script/CLI edition (originally developed as meetrec) — record, transcribe, and get notes entirely from the terminal, no app needed. It only requires the Xcode Command Line Tools and Python 3.10+ (no full Xcode):

Terminal window
git clone https://github.com/MeetGist/meetgist.git
cd meetgist
./setup.sh                 # checks prerequisites, builds the recorder, installs the terminal command
# add your key to scripts/.env:   GEMINI_API_KEY=your-key
source ~/.zshrc            # or just open a new terminal
meetgist                   # type once to start recording, again to stop + transcribe

./setup.sh installs the meetgist command plus helpers: gist-status, gist-open, gist-last, and gist-tx <file|folder> (transcribe existing audio); ./meetgist-toggle.sh is the same toggle if you prefer no aliases. Full script docs live in the GitHub README.

Next: grant permissions and add your API key, both inside the app.