v6.0.0

Version 6.0 puts names on your transcripts. A new People directory shows who spoke in which meeting, and a preview speaker model can tell remote participants apart. You can also run summaries on an AI server you already have, let other apps react when a meeting is done, and choose where your recordings and Markdown files are saved. Settings has been rebuilt to make room.

Highlights

People: know who said what

People is a new section in the sidebar. Assign a speaker in a transcript to a person, and their name replaces the label everywhere that meeting appears, including summaries and chat. Each person's page lists the meetings they spoke in, and global search (⌘K or Ctrl+K) finds them too.

• Names follow voices. Re-transcribe a meeting and assignments carry over when the match is unambiguous. If it isn't, MeetingDebrief keeps the assignment as it was rather than guess.
• No accidental duplicates. Renaming someone to a name that already exists offers a merge instead.
• Stale summaries are flagged. Naming a speaker marks that meeting's summary as out of date, so you can regenerate it with the right names.
• A clear reason when speakers can't be separated. If a transcript can't tell speakers apart, it now says why, such as a silent microphone, a single audio track or a missing model.

Tell remote speakers apart (preview)

Until now, everyone on the far end of a call was "Other". Turn on Tell remote speakers apart in Settings → Transcription and they become Speaker 1, Speaker 2 and so on, for up to four remote speakers. You can then assign each one to a person.

It runs on your machine, works with both Parakeet and Whisper, and needs a one-time model download. It works best in English and applies to new transcriptions. If it fails, the transcript falls back to Me and Other.

Run summaries on your own AI server

The built-in AI model takes several gigabytes of memory. Advanced users who already run llama.cpp, Ollama or LM Studio, locally or on another machine, can point MeetingDebrief at it in Settings → AI & Summaries: paste the address, add a token if it needs one, and click Test connection. Summaries, titles, chat and vocabulary suggestions then run on that server.

Your transcripts, notes and chat questions go to the server you choose, so pick one you trust. Audio doesn't: transcription always stays on your computer. The built-in model remains the default, and tokens are kept in your system's keychain.

I have been getting requests to support other AI servers and even online AI providers. If you run one that MeetingDebrief doesn't yet support and would like to see supported, please get in touch.

Integrations: let other apps react

Settings → Connections can now start a Zapier, Make or n8n flow, call Home Assistant, or run your own script (or a Shortcut on macOS) when a recording, transcript or summary finishes.

• Nothing is sent until you add an integration. By default it gets details only, such as ids, times and status. Sending meeting content is a separate choice for each integration.
• Limit it to some meetings by folder or tag, and pick which events it receives.
• Webhooks are signed using the Standard Webhooks spec, and brief outages are retried for up to 10 minutes. Anything older is dropped, so a laptop waking up the next morning doesn't replay yesterday.
• See what happened. Each integration has a Test button and a list of recent deliveries you can resend.

Local tools can also listen for events through GET /api/events on the API.

Choose where your files live

Settings → Storage lets you move recordings and the Markdown copies of your transcripts and summaries to a folder of your choice, such as an external drive or your Obsidian vault.

Recordings are always captured locally first and moved when they're finished, so an unplugged drive never costs you a meeting. Markdown files are only rewritten when their content changes, so edits you make in a notes app survive restarts.

Notes during the meeting, used in the summary

The notes field is now available while you record. Your notes go to summaries and chat as additional context, which helps with what mattered most to you and with names the transcript garbles. Custom templates can place them with a {notes} placeholder, and the API and MCP server can read them through a new get_notes tool.

A rebuilt Settings

Settings now has its own sidebar and shows one page at a time, grouped by what you're trying to do, with search across every setting. Some things have moved: models now live under Transcription and AI & Summaries, and feedback under About & Help.

Other improvements & fixes

• NEW: Dictations no longer include filler words and stutters like "um" and "uh". It's on by default, and you can turn it off with Remove filler words in Settings → Dictation.
• NEW: Insights shows the time dictation has saved you, compared with typing.
• On macOS, dictation only refuses to paste when the focused app holds Secure Input, and names the app. Failed pastes are harder to miss.
• Recordings now play as a centred mono mix, instead of your voice in one ear and the call in the other.
• Session titles follow the language of the summary.
• Failed sessions say why they failed, and tell "didn't start" apart from "transcription failed".
• If a saved system audio device disappears, recording uses the default output and tells you, instead of failing to start.
• Windows PCs with NVIDIA graphics download an updated Whisper GPU worker (over 200 MB) after updating. It brings Me and Other speaker labels and Vocabulary to GPU transcription with Whisper.
• Long meetings on Windows PCs with integrated graphics no longer run out of memory as easily. If they do, the summary retries with less memory, and otherwise shows a message you can act on.
• Progress toasts no longer get stuck when you leave a session during a job.
• The Move to menu stays visible for meetings near the bottom of the sidebar.
• MCP tools accept session ids from more clients and explain what's wrong when one is missing.