Getting started

Ogma is in alpha. On macOS you can download a prebuilt .dmg from the Releases page (see Installing on macOS below); on other platforms you build from source. iOS is planned.

Prerequisites

Rust (stable) — rustup.rs
Node.js (LTS)
The Tauri 2 prerequisites for your platform (on Windows: WebView2, which ships with Windows 11, and the MSVC build tools)
A microphone

Build and run

git clone https://github.com/davidlruizc/ogma.git
cd ogma
npm install
npm run tauri dev

npm run tauri dev starts the Vite dev server and compiles the Rust backend; the first build takes a few minutes.

For a release build:

npm run tauri build

Installing on macOS

Download Ogma_<version>_aarch64.dmg (Apple Silicon) from the Releases page, open it, and drag Ogma to Applications.

"Ogma is damaged and can't be opened"

If macOS shows this on first launch, the download is not corrupted. These alpha builds aren't yet notarized by Apple, so Gatekeeper blocks them — and because it's the "damaged" variant, there's no Open Anyway button. Clear the download quarantine flag once, from Terminal:

xattr -dr com.apple.quarantine /Applications/Ogma.app

Then open Ogma normally. This is a temporary step until the release is signed and notarized.

First launch checklist

Open Settings and paste your API keys — see Configuration. You need:
- an OpenAI key (Whisper transcription)
- an Anthropic key (speaker labels + notes)
- optionally a Notion integration token (sync)
Pick your microphone if you don't want the system default.
Hit record and say a few sentences with a colleague — a short 2-person conversation is the best smoke test.
Stop the recording and watch the pipeline run: transcribe → label & summarize → (optionally) sync to Notion.

Keys are required for processing, not recording

You can record without any API keys — audio is saved locally regardless. Transcription and notes run once keys are configured, and a failed or skipped step can always be retried later.

Where your data lives

Everything local is stored in the app data directory (on Windows: %APPDATA%\com.davidruiz.ogma):

Audio — WAV files per meeting, kept until the meeting is fully processed (and after — source audio is treated as sacred)
Database — a SQLite file holding meetings, transcripts (full-text indexed), notes, and action items
Config — config.json; API keys are stored in the OS keychain, not on disk (see Configuration)