Autoshelf Has an MCP Server You Probably Don't Need and The Rule Engine Is Weak - A Review
https://preview.redd.it/d00udd0gdbih1.jpg?width=1265&format=pjpg&auto=webp&s=7638f94d255eaf234386cfadd7cd4835645356e6
TL;DR: [AutoShelf](https://apps.apple.com/us/app/autoshelf-file-organizer/id6762361021?mt=12) ($19.99 one-time) ships an embedded MCP server that works, but do you actually need that? An AI model can write a launchd LaunchAgent and a shell script once and it runs forever, no app, no daemon, no purchase. The MCP's real value only shows up once you're managing enough rules to want conversational audit and editing instead of hand-maintained scripts, and even there, my hands-on testing found the rule engine underneath thin: no dynamic subfolder sorting, limited management by file size, and an action list a fraction of Hazel's. AutoShelf delivers less using AI than its marketing promises and loses the file-organizer argument outright.
# AutoShelf
I've had a [Hazel](https://www.noodlesoft.com) rule watching my Downloads folder since before I can accurately date it. It reads PDF invoices and files them by vendor, decompresses ZIPs and moves the app inside to Applications, converts HEICs to JPG, and hands ebooks to Calibre and audiobooks to Audiobookshelf without me touching any of it. That's the bar. A new license for Hazel is $42, which is steep for some and I've written before [about cheaper options](https://appaddict.app/post/hazel-alternatives). AutoShelf wants to be added to that list, and it's making its case with a feature none of those alternatives had: an MCP server for use with AI agents plus a CLI.
# More Than Just Simple File Management
* **An MCP server built into the app binary**, not a plugin bolted on after the fact. Point Claude Desktop, Cursor, Codex, or Windsurf at it and describe a rule in plain English instead of building it in a UI.
* **A companion CLI** for scripting rule creation and running jobs from the terminal, the same engine the MCP server talks to.
* **Where-from metadata as a condition**, so a rule can act on which browser or app downloaded a file, not just its type or name.
* **OCR and Live Text matching** as of version 2.2, so a rule can file a scanned invoice by what's written on it. Not new ground: Hazel's `Contents` attribute has done on-the-fly text recognition on images and text-layer-less PDFs for years, it's the mechanism behind the vendor-filing rule in the intro. AutoShelf catching up to a feature Hazel already had is parity, not an edge.
* **Multi-action, chainable rules**: move, tag, rename, and archive to ZIP in a single pass, added in the 2.0 rewrite.
# Is It Better Than Hazel for Working With AI?
Does anyone even need a layer between a prompt for file management and their file system? For a well-defined one-off job, not really. A capable AI model can write a launchd LaunchAgent with a `WatchPaths` key, native FSEvents, no polling loop, and a small shell script that switches on extension and moves the file. Write it once and it runs forever: no app, no background daemon, no $19.99. That's possible without Hazel or AutoShelf.
An MCP connection can do something a bespoke script can't: with it running, AutoShelf can immediately edit any rule with natural language, without you having to track down the launchd job and script you created six months ago. I created eight AutoShelf rules and asked Claude to check on them through the MCP connection; it returned current rules, current paths, and current enabled/disabled flags. A launchd script has no equivalent self-report; ask it "what are you doing" six months from now and the honest answer is "go read the shell and simulate it," and any edit needs a `launchctl unload`/`load` before it's live. MCP matters once you're managing enough rules that you'd rather audit, pause, or edit them by asking than by maintaining scripts by hand, or you want the GUI, activity log, and undo the app provides that a bare launchd job doesn't have unless you build it yourself.
Against Hazel specifically, AutoShelf is still ahead on this one front.
https://preview.redd.it/d00udd0gdbih1.jpg?width=1265&format=pjpg&auto=webp&s=7638f94d255eaf234386cfadd7cd4835645356e6
TL;DR: [AutoShelf](https://apps.apple.com/us/app/autoshelf-file-organizer/id6762361021?mt=12) ($19.99 one-time) ships an embedded MCP server that works, but do you actually need that? An AI model can write a launchd LaunchAgent and a shell script once and it runs forever, no app, no daemon, no purchase. The MCP's real value only shows up once you're managing enough rules to want conversational audit and editing instead of hand-maintained scripts, and even there, my hands-on testing found the rule engine underneath thin: no dynamic subfolder sorting, limited management by file size, and an action list a fraction of Hazel's. AutoShelf delivers less using AI than its marketing promises and loses the file-organizer argument outright.
# AutoShelf
I've had a [Hazel](https://www.noodlesoft.com) rule watching my Downloads folder since before I can accurately date it. It reads PDF invoices and files them by vendor, decompresses ZIPs and moves the app inside to Applications, converts HEICs to JPG, and hands ebooks to Calibre and audiobooks to Audiobookshelf without me touching any of it. That's the bar. A new license for Hazel is $42, which is steep for some and I've written before [about cheaper options](https://appaddict.app/post/hazel-alternatives). AutoShelf wants to be added to that list, and it's making its case with a feature none of those alternatives had: an MCP server for use with AI agents plus a CLI.
# More Than Just Simple File Management
* **An MCP server built into the app binary**, not a plugin bolted on after the fact. Point Claude Desktop, Cursor, Codex, or Windsurf at it and describe a rule in plain English instead of building it in a UI.
* **A companion CLI** for scripting rule creation and running jobs from the terminal, the same engine the MCP server talks to.
* **Where-from metadata as a condition**, so a rule can act on which browser or app downloaded a file, not just its type or name.
* **OCR and Live Text matching** as of version 2.2, so a rule can file a scanned invoice by what's written on it. Not new ground: Hazel's `Contents` attribute has done on-the-fly text recognition on images and text-layer-less PDFs for years, it's the mechanism behind the vendor-filing rule in the intro. AutoShelf catching up to a feature Hazel already had is parity, not an edge.
* **Multi-action, chainable rules**: move, tag, rename, and archive to ZIP in a single pass, added in the 2.0 rewrite.
# Is It Better Than Hazel for Working With AI?
Does anyone even need a layer between a prompt for file management and their file system? For a well-defined one-off job, not really. A capable AI model can write a launchd LaunchAgent with a `WatchPaths` key, native FSEvents, no polling loop, and a small shell script that switches on extension and moves the file. Write it once and it runs forever: no app, no background daemon, no $19.99. That's possible without Hazel or AutoShelf.
An MCP connection can do something a bespoke script can't: with it running, AutoShelf can immediately edit any rule with natural language, without you having to track down the launchd job and script you created six months ago. I created eight AutoShelf rules and asked Claude to check on them through the MCP connection; it returned current rules, current paths, and current enabled/disabled flags. A launchd script has no equivalent self-report; ask it "what are you doing" six months from now and the honest answer is "go read the shell and simulate it," and any edit needs a `launchctl unload`/`load` before it's live. MCP matters once you're managing enough rules that you'd rather audit, pause, or edit them by asking than by maintaining scripts by hand, or you want the GUI, activity log, and undo the app provides that a bare launchd job doesn't have unless you build it yourself.
Against Hazel specifically, AutoShelf is still ahead on this one front.
Hazel doesn't have an MCP server and doesn't claim to; anything an AI does to a Hazel rule today runs through a general-purpose file-editing layer poking at Hazel's XML underneath, which is fragile and unsupported. So among app-based rule engines with a GUI and an activity log, AutoShelf's MCP integration is real. On my Mac, it was easy to set up and worked as advertised on the first try.
# The Rule Engine Underneath Doesn't Hold Up
This is where my hands-on testing exposed the weaknesses in AutoShelf. It can't sort a folder of mixed files into subfolders by extension unless you create every destination subfolder yourself first and then write a separate rule for each file type. I had to build five nearly identical rules, "Sort PNG files," "Sort JPG files," "Sort JPEG files," "Sort GIF files," "Sort MD files," each one hand-built with its own hardcoded destination path. Hazel does the same job with a single "Sort into subfolder" action and a pattern; AutoShelf makes you write and maintain N rules for N extensions.
Two more gaps from my testing: size conditions only go down to whole megabytes, no decimal places, so you can't write a rule for anything under 1 MB or between whole-MB steps. More importantly, AutoShelf's action list (Move, Copy, Trash, Rename, Add Tag, Archive to ZIP, Optimize, Convert Image/Video/Audio, Photos import) is a fraction of Hazel's, which adds sync, upload, tags, color labels, comments, alias creation, three Music/Photos/TV import targets, and five different scripting hooks (Shortcuts, AppleScript, JavaScript, Automator, shell) on top of pause, notify, and rule-chaining controls.
# The Recursion Illusion
AutoShelf's App Store listing says it will "watch any folder you choose, including nested subfolders," and the 1.5 changelog calls it "Nested Folder Watching." [(App Store listing)](https://apps.apple.com/us/app/autoshelf-file-organizer/id6762361021?mt=12) But on its own Product Hunt launch, the developer told a commenter directly that watched folders are top-level only, files dropped into a subfolder are not picked up, and true recursion is a tracked feature request, not a shipped one. [(Product Hunt)](https://www.producthunt.com/products/autoshelf) Read charitably, "nested folder watching" means you can manually add specific subfolders you already know about as additional watch targets, one at a time. That is not the same as what Hazel does, which is recursive: add one "Run rules on folder contents" rule and Hazel will walk into subfolders of subfolders it has never seen, at any depth, applying your existing rules the whole way down. [(Noodlesoft manual)](https://www.noodlesoft.com/manual/hazel/advanced-topics/processing-subfolders/) That's a real discrepancy between AutoShelf's marketing copy and its confirmed current behavior, and now my own rule list shows the practical cost of it: I'm hand-maintaining what Hazel would do with one rule.
# Who This Is For, and Who Should Stay on Hazel
If your files land flat, one folder, no meaningful variety in file type, and you are considering a $19.99 one-time tool with a working AI hook, AutoShelf's free tier is worth an afternoon. If your needs are more complex, stick with Hazel. My own eight-rule test folder is the case study: if you have more than three or four file types, or anywhere the folder structure has depth, AutoShelf turns into more manual rule-building than the automation it's supposed to replace.
https://redd.it/1vjkxzl
@macappsbackup
# The Rule Engine Underneath Doesn't Hold Up
This is where my hands-on testing exposed the weaknesses in AutoShelf. It can't sort a folder of mixed files into subfolders by extension unless you create every destination subfolder yourself first and then write a separate rule for each file type. I had to build five nearly identical rules, "Sort PNG files," "Sort JPG files," "Sort JPEG files," "Sort GIF files," "Sort MD files," each one hand-built with its own hardcoded destination path. Hazel does the same job with a single "Sort into subfolder" action and a pattern; AutoShelf makes you write and maintain N rules for N extensions.
Two more gaps from my testing: size conditions only go down to whole megabytes, no decimal places, so you can't write a rule for anything under 1 MB or between whole-MB steps. More importantly, AutoShelf's action list (Move, Copy, Trash, Rename, Add Tag, Archive to ZIP, Optimize, Convert Image/Video/Audio, Photos import) is a fraction of Hazel's, which adds sync, upload, tags, color labels, comments, alias creation, three Music/Photos/TV import targets, and five different scripting hooks (Shortcuts, AppleScript, JavaScript, Automator, shell) on top of pause, notify, and rule-chaining controls.
# The Recursion Illusion
AutoShelf's App Store listing says it will "watch any folder you choose, including nested subfolders," and the 1.5 changelog calls it "Nested Folder Watching." [(App Store listing)](https://apps.apple.com/us/app/autoshelf-file-organizer/id6762361021?mt=12) But on its own Product Hunt launch, the developer told a commenter directly that watched folders are top-level only, files dropped into a subfolder are not picked up, and true recursion is a tracked feature request, not a shipped one. [(Product Hunt)](https://www.producthunt.com/products/autoshelf) Read charitably, "nested folder watching" means you can manually add specific subfolders you already know about as additional watch targets, one at a time. That is not the same as what Hazel does, which is recursive: add one "Run rules on folder contents" rule and Hazel will walk into subfolders of subfolders it has never seen, at any depth, applying your existing rules the whole way down. [(Noodlesoft manual)](https://www.noodlesoft.com/manual/hazel/advanced-topics/processing-subfolders/) That's a real discrepancy between AutoShelf's marketing copy and its confirmed current behavior, and now my own rule list shows the practical cost of it: I'm hand-maintaining what Hazel would do with one rule.
# Who This Is For, and Who Should Stay on Hazel
If your files land flat, one folder, no meaningful variety in file type, and you are considering a $19.99 one-time tool with a working AI hook, AutoShelf's free tier is worth an afternoon. If your needs are more complex, stick with Hazel. My own eight-rule test folder is the case study: if you have more than three or four file types, or anywhere the folder structure has depth, AutoShelf turns into more manual rule-building than the automation it's supposed to replace.
https://redd.it/1vjkxzl
@macappsbackup
App Store
AutoShelf - File Organizer App - App Store
Download AutoShelf - File Organizer by Orcun Ilbeyli on the App Store. See screenshots, ratings and reviews, user tips, and more apps like AutoShelf - File…
I built a voice typing app and need Mac users to tell me what’s wrong with it Giveaway: 3 months free
I'm Ozan, the developer of LipType.
Problem
I wanted voice typing that works anywhere on my Mac without opening a separate editor or copying text between apps. With LipType, you hold the Fn key, speak, release it, and the text appears where your cursor is.
Comparison
Apps like Wispr Flow and Superwhisper already do voice dictation well. LipType's approach is deliberately simple: system-wide dictation, task and notes support, and voice commands. It also has a Windows version. And we aim to keep the pricing as low as possible.
I know people here have tried most apps in this category, so I would genuinely like to hear where LipType is worse, not just where it is better.
Pricing
The free plan includes 2,000 words per week. Pro is $8 per month or $76.80 per year. The free plan does not require a credit card.
I'm having a hard time getting the first users, so I'd like to give three months of Pro to the first 10 people who are willing to use it during normal work for a week and tell me what is annoying, confusing, or missing.
You do not need to leave a review or say anything positive. Honest criticism is what I need.
If you want to try it, comment with the Mac app where you would use voice typing most.
Download: https://liptype.com/
Developer transparency
Ozan Kaşıkçı
GitHub: https://github.com/ozankasikci
LinkedIn: https://www.linkedin.com/in/ozankasikci
Contact: ozan@liptype.com
Privacy: https://liptype.com/privacy/
Terms: https://liptype.com/terms/
https://redd.it/1vjykmp
@macappsbackup
I'm Ozan, the developer of LipType.
Problem
I wanted voice typing that works anywhere on my Mac without opening a separate editor or copying text between apps. With LipType, you hold the Fn key, speak, release it, and the text appears where your cursor is.
Comparison
Apps like Wispr Flow and Superwhisper already do voice dictation well. LipType's approach is deliberately simple: system-wide dictation, task and notes support, and voice commands. It also has a Windows version. And we aim to keep the pricing as low as possible.
I know people here have tried most apps in this category, so I would genuinely like to hear where LipType is worse, not just where it is better.
Pricing
The free plan includes 2,000 words per week. Pro is $8 per month or $76.80 per year. The free plan does not require a credit card.
I'm having a hard time getting the first users, so I'd like to give three months of Pro to the first 10 people who are willing to use it during normal work for a week and tell me what is annoying, confusing, or missing.
You do not need to leave a review or say anything positive. Honest criticism is what I need.
If you want to try it, comment with the Mac app where you would use voice typing most.
Download: https://liptype.com/
Developer transparency
Ozan Kaşıkçı
GitHub: https://github.com/ozankasikci
LinkedIn: https://www.linkedin.com/in/ozankasikci
Contact: ozan@liptype.com
Privacy: https://liptype.com/privacy/
Terms: https://liptype.com/terms/
https://redd.it/1vjykmp
@macappsbackup
LipType
LipType - AI-Powered Voice to Text | 99% Accuracy Speech Recognition
Transform your speech into perfect text with 99% accuracy. Advanced AI voice recognition for professionals, content creators, and businesses.
This media is not supported in your browser
VIEW IN TELEGRAM
I made a Mac screenshot tool that compresses images before sending them to Claude / Codex
https://redd.it/1vk1xf7
@macappsbackup
https://redd.it/1vk1xf7
@macappsbackup
Media is too big
VIEW IN TELEGRAM
1 year of ShiftPlus (my solo macOS workspace switcher), ~1,300 downloads, here's what shipped since 2.0
https://redd.it/1vk9w80
@macappsbackup
https://redd.it/1vk9w80
@macappsbackup
This media is not supported in your browser
VIEW IN TELEGRAM
CodeSwissKnife 2.0 - a private, local developer toolbox for macOS
https://redd.it/1vkeu0e
@macappsbackup
https://redd.it/1vkeu0e
@macappsbackup
This media is not supported in your browser
VIEW IN TELEGRAM
Refine: A Grammarly alternative that runs 100% offline (13-month update)
https://redd.it/1vkmk39
@macappsbackup
https://redd.it/1vkmk39
@macappsbackup
This media is not supported in your browser
VIEW IN TELEGRAM
A little update to WidgetScreen: I’ve added live lyrics and a news widget.
https://redd.it/1vkkwvc
@macappsbackup
https://redd.it/1vkkwvc
@macappsbackup
This media is not supported in your browser
VIEW IN TELEGRAM
Unfold (v2.8.0) - Quick Look for Folders, Archives, Source Code, LaTeX, Ebooks and More 🌟
https://redd.it/1vkmke9
@macappsbackup
https://redd.it/1vkmke9
@macappsbackup
This media is not supported in your browser
VIEW IN TELEGRAM
I built an app that turns the song you're listening to into an animated vinyl wallpaper
https://redd.it/1vkogct
@macappsbackup
https://redd.it/1vkogct
@macappsbackup
This media is not supported in your browser
VIEW IN TELEGRAM
Mousio v3.0 is out! Control mouse movement, clicks and drags via your keyboard, with a keyboard-triggered Launchpad built-in.
https://redd.it/1vksj3k
@macappsbackup
https://redd.it/1vksj3k
@macappsbackup
This media is not supported in your browser
VIEW IN TELEGRAM
Workflo: Mac window layouts that switch automatically for meetings, focus blocks, and displays
https://redd.it/1vki7o5
@macappsbackup
https://redd.it/1vki7o5
@macappsbackup
Caption Snap: Meeting Transcriptions With No Bot, No Model to Download, No Data Transferred and No Drain on Your CPU - Free Trial, One Time, $9.99
https://preview.redd.it/94qw11zt5kih1.jpg?width=1069&format=pjpg&auto=webp&s=b318fd2e6f9ed534aec652923069f9504dfa1625
**TL;DR:** CaptionSnap is a $9.99 one-time menu bar app that saves your Teams, Zoom, and Google Meet transcripts by reading the live captions the meeting app already displays. No audio recording, no bot in the call, no cloud, no model download, and Accessibility is the only permission it asks for. Speaker names come from the platform, so attribution is a lookup instead of a guess. You have to enable captions yourself, transcripts are only as good as the platform's captioning, and it requires macOS 26 on Apple Silicon.
# CaptionSnap Reads the Captions Your Meeting App Already Shows You
Here is a list of the many things I don't like about transcription apps.
* Using one in a meeting often means a bot joins the call and you have to explain it to everyone.
* Local models require a huge download.
* Remote models send my conversations to somebody else's server.
* They require numerous privacy and security exemptions.
* Local models are processor intensive.
Well, I found an app that doesn't do any of those things and still delivers better-than-average accuracy while using a tiny percentage of my CPU. It's called [CaptionSnap](https://captionsnap.app/).
# The trick
Teams, Zoom, and Google Meet already transcribe your meeting. That's what live captions are. The text is right there on screen, generated by the platform, attached to the correct speaker, and then thrown away the second the call ends.
Every other tool in this category ignores that and starts over from scratch. Record the audio, run it through a model, guess at who said what, hope the diarization holds up. CaptionSnap just reads the captions the meeting app is already displaying and writes them to a Markdown file with timestamps and the speaker names the platform supplied.
That one decision is the premise for the whole app. It's why there's no model download, no audio pipeline, no microphone prompt, and no bot in your call. There's nothing to overcharge you for.
# What that buys you
**Real speaker names, not guesses.** The names come from the meeting platform, so "who said that" is a lookup, not an inference. Whisper-based tools get diarization wrong constantly on four-person calls with crosstalk. This sidesteps the problem instead of solving it.
**One permission.** Accessibility. That's it. No Screen Recording, no microphone, no camera ([CaptionSnap FAQ](https://captionsnap.app/)). If you've ever watched a meeting app collect four permissions on the way in, you know why that matters.
**Minimal CPU.** Not a tuning achievement. There's no neural network running, so there's nothing to burn cycles on. Your fans stay quiet and your battery survives a day of calls.
**Plain Markdown on your disk.** No account, no sync, no server, no export step. The developer claims the app makes no network connections at all ([CaptionSnap homepage](https://captionsnap.app/)). Optional summaries run through Apple Intelligence on-device.
**It works behind other windows.** The meeting can sit in the background while you do actual work, and the transcript keeps filling in.
# What it does not do
* It does not turn captions on for you. Live captions are off by default in Teams, Zoom, and Meet, and you have to flip that switch yourself before CaptionSnap has anything to read ([CaptionSnap FAQ](https://captionsnap.app/)).
* It does not record audio, so there's no recording to go back to when the transcript is wrong.
* It does not fix bad captions. If Teams mangles a name or drops a clause, that lands in your file exactly as mangled. Your transcript is only as good as the platform's captioning, and the marketing line "accurate by design, not guesswork" is about who said what, not about the words.
* It does not run on Intel, and it does not run below macOS 26. Apple Silicon and Tahoe or nothing. (I have not tested it on
https://preview.redd.it/94qw11zt5kih1.jpg?width=1069&format=pjpg&auto=webp&s=b318fd2e6f9ed534aec652923069f9504dfa1625
**TL;DR:** CaptionSnap is a $9.99 one-time menu bar app that saves your Teams, Zoom, and Google Meet transcripts by reading the live captions the meeting app already displays. No audio recording, no bot in the call, no cloud, no model download, and Accessibility is the only permission it asks for. Speaker names come from the platform, so attribution is a lookup instead of a guess. You have to enable captions yourself, transcripts are only as good as the platform's captioning, and it requires macOS 26 on Apple Silicon.
# CaptionSnap Reads the Captions Your Meeting App Already Shows You
Here is a list of the many things I don't like about transcription apps.
* Using one in a meeting often means a bot joins the call and you have to explain it to everyone.
* Local models require a huge download.
* Remote models send my conversations to somebody else's server.
* They require numerous privacy and security exemptions.
* Local models are processor intensive.
Well, I found an app that doesn't do any of those things and still delivers better-than-average accuracy while using a tiny percentage of my CPU. It's called [CaptionSnap](https://captionsnap.app/).
# The trick
Teams, Zoom, and Google Meet already transcribe your meeting. That's what live captions are. The text is right there on screen, generated by the platform, attached to the correct speaker, and then thrown away the second the call ends.
Every other tool in this category ignores that and starts over from scratch. Record the audio, run it through a model, guess at who said what, hope the diarization holds up. CaptionSnap just reads the captions the meeting app is already displaying and writes them to a Markdown file with timestamps and the speaker names the platform supplied.
That one decision is the premise for the whole app. It's why there's no model download, no audio pipeline, no microphone prompt, and no bot in your call. There's nothing to overcharge you for.
# What that buys you
**Real speaker names, not guesses.** The names come from the meeting platform, so "who said that" is a lookup, not an inference. Whisper-based tools get diarization wrong constantly on four-person calls with crosstalk. This sidesteps the problem instead of solving it.
**One permission.** Accessibility. That's it. No Screen Recording, no microphone, no camera ([CaptionSnap FAQ](https://captionsnap.app/)). If you've ever watched a meeting app collect four permissions on the way in, you know why that matters.
**Minimal CPU.** Not a tuning achievement. There's no neural network running, so there's nothing to burn cycles on. Your fans stay quiet and your battery survives a day of calls.
**Plain Markdown on your disk.** No account, no sync, no server, no export step. The developer claims the app makes no network connections at all ([CaptionSnap homepage](https://captionsnap.app/)). Optional summaries run through Apple Intelligence on-device.
**It works behind other windows.** The meeting can sit in the background while you do actual work, and the transcript keeps filling in.
# What it does not do
* It does not turn captions on for you. Live captions are off by default in Teams, Zoom, and Meet, and you have to flip that switch yourself before CaptionSnap has anything to read ([CaptionSnap FAQ](https://captionsnap.app/)).
* It does not record audio, so there's no recording to go back to when the transcript is wrong.
* It does not fix bad captions. If Teams mangles a name or drops a clause, that lands in your file exactly as mangled. Your transcript is only as good as the platform's captioning, and the marketing line "accurate by design, not guesswork" is about who said what, not about the words.
* It does not run on Intel, and it does not run below macOS 26. Apple Silicon and Tahoe or nothing. (I have not tested it on
the macOS 27 Golden Gate beta.)
# The potential gotcha
CaptionSnap has to be running in your menu bar when the meeting starts. It does not turn on captions in Teams, Google Meet, or Zoom for you, so that's your job too. CaptionSnap provides instructions for each platform. As long as you don't disable captions later, the setting should hold between restarts of each app, but verify it yourself. The worst version of this is finding out after the meeting that nothing was captured.
# Who this is for
This is for you if you take meeting notes on a Mac, you don't want a bot announcing itself in a client call, and you'd rather have a plain text file than a web dashboard. If you aren't fond of explaining to IT why you need an app with Screen Recording permission, CaptionSnap doesn't put you in that conversation.
# Who this is not for
This is not for you if you need the audio and not just the text, or if you work with people who never enable captions. Don't get it if you're on Intel or an older macOS, or if you want AI-generated action items and CRM sync. For that last one, this is deliberately the wrong tool and the subscription products below are the right ones.
# The alternatives
**macOS Live Captions.** Free, built in. Vanishes when you dismiss it, no speaker names, no timestamps, nothing saved. Useful in the moment, useless a day later.
**MacWhisper.** Free tier, or €64 one-time for Pro ([macwhisper.com](https://www.macwhisper.com/)). Transcribes local audio with Whisper and Parakeet, records Zoom, Teams, Webex, Skype, and Discord without a bot, and Pro includes automatic meeting start and end detection plus speaker recognition. Much larger tool, much larger job. It does the model download and the CPU work that CaptionSnap avoids, and in exchange it also handles interviews, lectures, podcasts, and system-wide dictation. If you need transcription generally and not just meetings, this is the one. I wrote about it in 2024: [MacWhisper - Transcription Powerhouse](https://appaddict.app/post/macwhisper-transcription-powerhouse).
**Granola.** Free Basic tier with limited history, $14 per user per month for Business, $35 for Enterprise ([granola.ai/pricing](https://www.granola.ai/pricing)). Also avoids joining as a bot, but it processes in the cloud and is built around AI-enhanced notes and team integrations rather than a raw transcript you own.
**Otter.ai.** Free tier at 300 minutes per month, Pro at $16.99 per user per month billed monthly or $8.33 billed annually, Business at $30 monthly or $19.99 annually ([otter.ai/pricing](https://otter.ai/pricing)). This is the thing CaptionSnap is reacting to: it joins your Zoom, Teams, and Meet calls as a notetaker, and everything lives on Otter's servers. I've used Otter for dictation, but not for meetings.
Unless otherwise noted, the alternate apps mentioned above are based on research and not individual testing.
# Price and verdict
Fourteen-day trial, no credit card, then $9.99 once for up to three Macs, with a 30-day refund policy ([CaptionSnap pricing](https://captionsnap.app/)). Ten dollars, paid one time, against $14 to $17 a month for the subscription notetakers.
This is Wes Stockfisch's first shipped app. I give developers the benefit of the doubt, but be aware, there's no maintenance track record here, and the macOS 26 plus Apple Silicon requirement means you need a current M-series machine. But the idea is right. The captions already exist. Reading them instead of recreating them is the kind of obvious move nobody made because, well, they mnight have been overthinking it on this..
One caveat before the verdict: I haven't been able to test this extensively. Retirees don't have a lot of Zoom calls. But in the testing I was able to do, CaptionSnap held up.
In my opinion, ten dollars to stop explaining a bot to clients is not a hard decision.
https://redd.it/1vkmkai
@macappsbackup
# The potential gotcha
CaptionSnap has to be running in your menu bar when the meeting starts. It does not turn on captions in Teams, Google Meet, or Zoom for you, so that's your job too. CaptionSnap provides instructions for each platform. As long as you don't disable captions later, the setting should hold between restarts of each app, but verify it yourself. The worst version of this is finding out after the meeting that nothing was captured.
# Who this is for
This is for you if you take meeting notes on a Mac, you don't want a bot announcing itself in a client call, and you'd rather have a plain text file than a web dashboard. If you aren't fond of explaining to IT why you need an app with Screen Recording permission, CaptionSnap doesn't put you in that conversation.
# Who this is not for
This is not for you if you need the audio and not just the text, or if you work with people who never enable captions. Don't get it if you're on Intel or an older macOS, or if you want AI-generated action items and CRM sync. For that last one, this is deliberately the wrong tool and the subscription products below are the right ones.
# The alternatives
**macOS Live Captions.** Free, built in. Vanishes when you dismiss it, no speaker names, no timestamps, nothing saved. Useful in the moment, useless a day later.
**MacWhisper.** Free tier, or €64 one-time for Pro ([macwhisper.com](https://www.macwhisper.com/)). Transcribes local audio with Whisper and Parakeet, records Zoom, Teams, Webex, Skype, and Discord without a bot, and Pro includes automatic meeting start and end detection plus speaker recognition. Much larger tool, much larger job. It does the model download and the CPU work that CaptionSnap avoids, and in exchange it also handles interviews, lectures, podcasts, and system-wide dictation. If you need transcription generally and not just meetings, this is the one. I wrote about it in 2024: [MacWhisper - Transcription Powerhouse](https://appaddict.app/post/macwhisper-transcription-powerhouse).
**Granola.** Free Basic tier with limited history, $14 per user per month for Business, $35 for Enterprise ([granola.ai/pricing](https://www.granola.ai/pricing)). Also avoids joining as a bot, but it processes in the cloud and is built around AI-enhanced notes and team integrations rather than a raw transcript you own.
**Otter.ai.** Free tier at 300 minutes per month, Pro at $16.99 per user per month billed monthly or $8.33 billed annually, Business at $30 monthly or $19.99 annually ([otter.ai/pricing](https://otter.ai/pricing)). This is the thing CaptionSnap is reacting to: it joins your Zoom, Teams, and Meet calls as a notetaker, and everything lives on Otter's servers. I've used Otter for dictation, but not for meetings.
Unless otherwise noted, the alternate apps mentioned above are based on research and not individual testing.
# Price and verdict
Fourteen-day trial, no credit card, then $9.99 once for up to three Macs, with a 30-day refund policy ([CaptionSnap pricing](https://captionsnap.app/)). Ten dollars, paid one time, against $14 to $17 a month for the subscription notetakers.
This is Wes Stockfisch's first shipped app. I give developers the benefit of the doubt, but be aware, there's no maintenance track record here, and the macOS 26 plus Apple Silicon requirement means you need a current M-series machine. But the idea is right. The captions already exist. Reading them instead of recreating them is the kind of obvious move nobody made because, well, they mnight have been overthinking it on this..
One caveat before the verdict: I haven't been able to test this extensively. Retirees don't have a lot of Zoom calls. But in the testing I was able to do, CaptionSnap held up.
In my opinion, ten dollars to stop explaining a bot to clients is not a hard decision.
https://redd.it/1vkmkai
@macappsbackup
appaddict.app
MacWhisper - Transcription Powerhouse
I made my first purchase of the 2024 Black Friday season by purchasing the transcription app, MacWhisper by indy developer Jordi Bruin for 40% off of the usual price of €49.99. This app uses OpenAI's Whisper technology to transcribe all types of audio files…