Meeting notes, local on your Mac by default

TL;DR

• WalkAITalkie’s meeting/session notes mode is part of Pro. Transcription and notes run on your Mac by default.
• Speech recognition always stays on-device. In local mode, neither audio nor transcripts go to a model provider.
• Only the direct version with Pro can accelerate summaries through your own Codex or Claude Code CLI, after you explicitly enable it. It sends text, never audio.
• Speaker diarization separates who said what, and an optional mailto draft closes out the workflow.
• WalkAITalkie has a Mac App Store version and a direct version from walkaitalkie.com or Homebrew. Pro is a one-time purchase; the App Store version has no cloud accelerator.

The privacy problem with cloud notetakers

Otter and Granola solve a real problem. You sit in a meeting, you want to listen instead of scribbling notes, and at the end you still get a usable summary. That works well, and I understand why so many teams use these tools every day.

With cloud processing, the data path depends on which part of the workflow runs on a server. That might be audio for transcription or text for summarization. For me, the concrete question is what leaves my machine, and whether I enabled that path myself.

For a lot of meetings that is fine. For others it is not. A client call with contract details, an internal roadmap discussion, a conversation with legal or personnel sensitivity: once that content lands on someone else's infrastructure, confidentiality depends on a privacy policy, a retention window and a security practice you do not control. Most vendors are careful about this. But "careful" is not the same as "not possible in the first place".

That is the point where I want a local default. For sensitive content, I want to process the recording and text on my Mac. I applied the same principle in the local mail assistant built on Apple Foundation Models.

There is a second, more practical concern: a workflow that needs an external provider depends on its availability and terms. For sensitive conversations, I want to decide for myself whether to take on that dependency.

Meeting Mode: transcription always local, summaries local by default

This is where WalkAITalkie’s meeting/session notes mode comes in. WalkAITalkie is my macOS menu-bar app for push-to-talk dictation. It is one product in two channels: the Mac App Store and a direct version from walkaitalkie.com or Homebrew. Meeting/session notes is part of Pro and extends the same principle from dictation to in-person meetings.

The flow is deliberately simple. You start recording from the menu bar, as you would for regular dictation. Your Mac’s microphone picks up the conversation in the room, with no separate meeting tool or bot joining a video call. Speech recognition always runs directly on the device. Whether local processing is practical on my Mac also depends on model size: a large coding model on the same machine is precisely where I ran into the wall.

From the raw transcript comes a structured summary: minutes of what was discussed, clearly organized notes, and a list of action items. This text processing also runs on the Mac by default. In local mode, neither audio nor transcripts go to a model provider. After the model download, this path works offline.

If you want to accelerate summaries, you can explicitly enable the cloud accelerator in the direct version with Pro. It hands text, never audio, to the Codex or Claude Code CLI you are already signed in to. The text goes to your provider, on your plan, not to me. The App Store version has no accelerator. Without enabling it, processing stays local.

Speaker diarization and the mailto draft as the finishing step

Minutes without recognizable speakers are only half useful. Who made the proposal, who agreed to which follow-up? That is why speaker diarization runs alongside the transcription: the system distinguishes which passages came from which person in the room and attributes statements accordingly. That makes the minutes readable, not just complete.

At the end of the workflow sits an optional email draft. WalkAITalkie opens a mailto link that launches your default mail client with a pre-filled draft, subject, summary, action items. Nothing is sent automatically, no cloud email API running in the background. You see the draft, review it, adjust whatever is needed, and send it through your own mail app. The follow-up step that so often gets skipped after a meeting is done in seconds, without any intermediate step giving up your control over sending it.

That choice to stay with mailto instead of a direct send integration follows the same principle as the transcription itself. A direct send through a cloud API would mean storing credentials to your mail account somewhere, and routing the finished text through yet another service before it gets sent. The mailto detour is marginally less convenient, one extra click, but it keeps control over the final word entirely with you. For an internal recap that might not matter much. For a summary with confidential details, it is the difference between "I sent it" and "it was sent for me".

The format library: one workflow, many output shapes

What sits behind Meeting Mode is not limited to meetings. Recording and transcription stay local; structured summaries also happen on the Mac by default. Meeting minutes are one output format, but the architecture generalizes into a format library. Explicitly enabling the cloud accelerator changes where the text is processed, while audio stays local.

Concretely: the same workflow that turns a meeting into minutes can turn a different recording into a different structure. One example that convinced me is the to-do list. You speak your thoughts, and instead of a generic transcript, you get a list of the tasks, one per line, rather than running text. The underlying logic stays the same: recording in, matching structure out. Which format makes sense depends on the use case, not on the underlying technology.

That generalization is the part that makes WalkAITalkie more interesting to me than a pure meeting tool. It is a reusable pattern: local speech recognition with an interchangeable output structure. New formats do not need new core infrastructure. The recording and transcription pipeline stays the same; only the summary template changes with the context you are capturing. The recording stays on the device. Text processing follows the same choice as meeting minutes: local by default, or through your own provider with the cloud accelerator explicitly enabled.

Distribution: App Store and direct version

WalkAITalkie has a Mac App Store version and a direct version available from walkaitalkie.com or Homebrew. Meeting/session notes is part of Pro. Pro is a one-time purchase: a non-consumable in-app purchase in the App Store, or a Stripe license for the direct version.

WalkAITalkie needs no account or login. There is no subscription, no credits, and no cloud processing operated by me. The optional cloud accelerator belongs exclusively to the direct version with Pro and uses the CLI the user is already signed in to. Their provider and plan remain separate; the App Store version has no such path.

Why I want local processing as the default

You can compare meeting-notes tools on plenty of axes: transcription quality, summary style, integration with calendars and note apps, price. On most of those axes, there are good cloud solutions, and Granola or Otter do things today that WalkAITalkie does not yet do.

What matters to me is that I can choose the local path: audio and transcripts then stay away from model providers. Enabling the cloud accelerator is a deliberate choice to process text with my own provider. Speech recognition stays on the Mac in either case.

As a solo builder, I want to use local mode for confidential client conversations without depending on an external model provider. For other conversations, acceleration through my own CLI can make sense. That decision should be mine before text leaves the device.

Conclusion

Meeting Mode is my way of turning a recording into usable minutes. Speech recognition always stays on the Mac, with notes and summaries processed there by default too. Only in the direct version with Pro can I explicitly enable text processing through my own Codex or Claude Code CLI. Meeting/session notes is part of Pro, a one-time purchase. The format library carries the same workflow into other output structures.

If you are curious, you can find WalkAITalkie at walkaitalkie.com. And if you want to know how I build on-device tools into real workflows beyond meeting notes: the contact section is the direct route.