An automatic meeting notes pipeline is four stages in a row: capture turns the meeting into audio, transcription turns the audio into text with timestamps and speakers, summarizing turns that into structured notes, and filing puts the notes where you will find them. People build this on a Mac with a recorder, a speech model, a language model, a folder watcher and a few hundred lines of script.
You can get the same chain without the scripts. ThinkScribe for Mac records the call audio and your microphone together, transcribes on your Mac with speakers told apart, writes the summary for each new recording as soon as it is transcribed, and exports Markdown or shares to Apple Notes. This guide explains what each stage has to get right, whichever way you build it, then sets it up in ThinkScribe.
Four stages, kept separate
The design decision that matters most is that each stage produces something you can open and check: an audio file, a transcript, a summary, a note. A single pass that does everything in memory works on a good day and is miserable on a bad one. If the last step fails, you lose the transcript that took the longest to make. Separate stages are resumable (a failure at the end leaves earlier results in place), debuggable (when a summary is wrong, open the transcript and see which one was at fault) and repeatable (re-summarize with better instructions without transcribing again).
| Stage | Takes | Produces | In ThinkScribe for Mac |
|---|---|---|---|
| 1. Capture | The meeting | An audio recording | Microphone and System audio in one recording |
| 2. Transcribe | The audio | Text with timestamps and speakers | Transcript made on your Mac when you stop |
| 3. Summarize | The transcript | Structured notes | Summary, Meeting Minutes, Action Items |
| 4. File | The notes | A note in your notes app | Export as Markdown, PDF, Word, or Share to Notes |
Stage 1: capture
macOS does not record what comes out of your speakers on its own, which is why meeting capture is its own problem. In ThinkScribe for Mac, the record bar has two source toggles, Microphone and System audio, and system audio captures Zoom, Teams, FaceTime and other app audio. The menu bar offers Record Meeting (Mic + App) for the usual case, and Record App Audio Only when you only want the other side. No meeting bot joins the call. Record a Zoom, Teams or Meet call on Mac without a bot covers the permission and the options.
Tell the other participants you are recording, and follow the consent rules where you and they are.
Stage 2: transcribe, and keep the timestamps
Timestamps cost nothing and are the only route back to the audio. When someone disputes what was agreed, a line you can play from is worth more than any summary. Speaker labels matter nearly as much: a summarizer that knows who said what can attribute decisions to people instead of writing "it was decided".
ThinkScribe makes the full transcript after you stop, on your Mac, and separates speakers automatically as Speaker 1, Speaker 2 and so on. Rename a speaker once and every line with that label updates; named voices are then recognized in new recordings. Speaker diarization on a Mac explains how this works. For names and jargon that keep coming out wrong, add them to Settings > Vocabulary.
Stage 3: summarize without inventing
Most of the quality in machine-written notes comes from what the summarizer is told to do. Whoever builds the pipeline, the same rules hold:
- Use only what is in the transcript. The anti-invention rule matters more than any other.
- Give it a way to say "nothing". A status call with no decisions should produce "none recorded", not three made-up action items.
- Keep disagreement as disagreement. Summarizers are trained to be agreeable and will turn "I think that is the wrong call" into "the team aligned".
- An action item is something someone accepted. A passing "maybe we should email the vendor" is an open question, not a task with an owner.
- Keep names, numbers and dates exactly. These are the details a summary smooths away and the ones you will need.
- Use fixed sections. Summary, decisions, action items, open questions, so notes from different meetings look alike.
In ThinkScribe, a recording offers Summarize, Meeting Minutes and Executive Brief, and the summary includes an Action Items list. Summary points carry citations you can click to jump to the line in the transcript, so a claim can be checked in seconds. Each result can be edited or tried again. Meeting minutes and action items from a recording goes deeper on the formats.
Stage 4: file it
Markdown-based notes apps, a plain folder included, only need a .md file dropped into the right place. That is why Markdown is the most durable format to file meeting notes in: no plugin, no account, readable in twenty years. Hosted notes services need their own import or API, which is real work to maintain.
From ThinkScribe for Mac you can export a transcript as Markdown, Plain Text, PDF, Word Document, JSON, CSV, or SRT and VTT subtitles, and Share to Notes sends it to Apple Notes. Export a transcript lists what each format contains.
What a hand-built pipeline involves
If you script the chain yourself, the honest picture looks like this:
- Tools for every stage. A recorder that can capture system audio, a speech model, a language model with enough memory for long transcripts, and glue code for the formats between them.
- A folder watcher that misses things. Apple's own documentation for launchd warns that watching a folder is race-prone: events can be missed, and a file can still be half-written when the job starts. A reliable script checks that a file has stopped growing, remembers what it already processed, and survives running twice.
- Long meetings. An hour of talk is around 12,000 tokens, more than many language models accept by default, so long transcripts have to be split and summarized in stages.
- Silent failures. A moved model file, a full disk or a changed setting, and the job dies at 2 a.m. without telling you.
- Upkeep. Tool flags, model names and notes APIs change. None of it is hard; all of it lands on you, usually on the morning you needed the notes.
How to set up automatic meeting notes in ThinkScribe on a Mac
ThinkScribe for Mac runs on a Mac with Apple silicon and macOS 26 or later.
- During the first run, allow Microphone and System Audio on the Permissions step. Optionally, turn on Notify when call starts in Settings > Recording so you get a nudge when a call begins.
- When the meeting starts, choose Record Meeting (Mic + App) from the menu bar, or start a recording with both Microphone and System audio on in the record bar.
- When it ends, stop with Stop Recording (⌘.). The transcript is made on your Mac, with speakers separated.
- Open the recording and choose Summarize for a summary with action items, or Meeting Minutes for the fuller version.
- Rename speakers once so their names carry into future meetings, then Export as Markdown into your notes folder or use Share to Notes.
- For recordings made elsewhere, choose Import File... (⌘I) or drag several files onto the window, and turn on Auto-Export After Transcription so each one is exported when it finishes.
If several meetings belong together, put them in a collection and ask questions across all of them. The meeting transcription page shows the whole flow, and the complete guide to voice to text covers iPhone, iPad and Apple Watch too.
What still goes wrong, whoever built it
- One recording, three meetings. Two people chat before the start, the meeting runs, three stay after. The summary treats it as one event. Trim or ignore the edges.
- Invented action items. Clear rules reduce them; they do not remove them. Check anything with a name and a deadline against the cited line.
- Crosstalk. When people talk over each other, both the transcript and the speaker labels get worse. A decent microphone near the speakers helps more than any setting.
Frequently asked questions
How do I automatically turn a meeting recording into notes on a Mac?
Record the call with ThinkScribe for Mac using microphone and system audio together. When you stop, the transcript is made on your Mac; summarize it in one click. Export it as Markdown into your notes folder or share it to Apple Notes.
Does a bot need to join the call?
No. ThinkScribe records the audio your Mac plays and your microphone, so nothing joins the meeting and the other participants see no extra attendee. Tell them you are recording and follow your local consent rules.
Can meeting notes go into Obsidian or Apple Notes?
Yes. Export the transcript as Markdown and save it into your vault or notes folder, or use Share to Notes on the Mac to send it to Apple Notes. Batch imports can export automatically with Auto-Export After Transcription.
Why keep timestamps if the summary does not show them?
They are the link back to the audio. A decision you can play from its exact line can be checked in seconds, and a strange sentence can be traced to real speech or to silence. In ThinkScribe, summary citations jump straight to the line.
How do I stop a summarizer inventing action items?
Define an action item as something a named person accepted, give the summarizer a way to report "none", and check the transcript behind every task. In ThinkScribe, click the citation on a summary point to see the line it came from, and use Edit or Retry when it is wrong.
