On-Device Meeting Transcription and Summary: What Oris Writes

After a meeting ends, Oris writes the notes back into your Markdown workflow. The content lands in the note associated with that recording — or, if that can’t be resolved, in your configured folder as a fallback file. Either way, it stays in Markdown, where the rest of your notes already live.

Here’s what comes back: when summarization runs and succeeds, a structured summary with callouts for decisions, action items, and open questions, plus the full transcript.

What the output looks like

The summary comes first. A brief overview and structured breakdown — enough to reconstruct what the meeting was about, who drove it, and where it ended up. Organized around what came out of the meeting, with decisions and action items called out so they don’t get buried in paragraphs of recap. If there’s nothing substantive to report in a given category, that part doesn’t appear.

Below that, the full transcript: timestamped, your side and theirs labeled separately, tucked so it’s out of the way when you don’t need it. Oris captures both sides of a call directly on your Mac, so the transcript isn’t reconstructed from one side.

Transcription runs on-device. The audio never leaves your machine. Summarization runs on-device by default too — Oris picks local for you. Bring your own API key in Settings if you’d rather use a cloud model.

Why decisions get their own callout

The transcript is there for when something gets disputed two weeks later — you go back and check it. Most of the time, though, you’re not re-reading 45 minutes of back-and-forth to check what got decided.

The problem with most meeting notes is that everything gets flattened. Decisions, open questions, side conversations, and things someone said they might consider someday all end up in the same list or paragraph. You can’t skim it. You have to read through the whole thing to find the one sentence that matters.

A dedicated decisions callout changes how you use the notes. You open them, read the decisions in 30 seconds, and either close it or drop into the transcript for context. The summary covers everything in between.

The model extracts decisions from the full conversation rather than waiting for you to write them down during the meeting. It’s best-effort: most decisions surface, even ones nobody explicitly announced, but check the transcript for anything that really matters. Because the model works from the full transcript, both sides of the conversation are in scope.

Getting the output into your vault

In Settings, you point Oris at a folder: your Obsidian vault, a plain directory, anywhere you keep .md files. After each meeting, the content is written there — into the note associated with that recording, or as a new file in the folder if that note can’t be found. From there it behaves like any other Markdown: you can link to it, search it, tag it, or pull it into a template.

Summarization runs on-device by default — Oris picks local for you. Bring your own API key in Settings if you’d rather use a cloud model.

The output is a record you’ll actually use. Summary first, because that’s what you read after every meeting. Decisions called out, because that’s what you recheck a week later. Transcript available, because that’s what you search when it matters.