Show HN: AutoPause – macOS utility that auto-pauses media when mic is in use

4 visualstackk 3 8/7/2025, 1:00:05 PM apps.apple.com ↗
I often listen to Spotify or YouTube while working, but every time I joined a quick Slack call or used voice dictation, I had to scramble to pause my music and then remember to resume it afterwards (this is made worse by headphones on OSX switching to Bluetooth audio profiles when the mic is in use - if you know you know )

I built AutoPause to remove that step. It’s a small macOS menu bar app that detects when your microphone is in use and automatically pauses your music or video, resuming when the mic is free.

Features: - Works with Spotify, Apple Music, YouTube, Netflix, and more. - Browser media support via a companion Chrome extension. - Local-only: the macOS app and Chrome extension communicate via WebSockets on localhost; nothing leaves your machine.

App Store link: https://apps.apple.com/us/app/autopause/id6747332615?ct=hn-s...

I’ve been a software engineer for 15 years or so, but I fully vibe-coded this as a trial (and then had to undo most of it at least once lol).

Built in Swift (AppKit) with a lightweight Chrome extension that handles browser media control.

Happy to answer questions or hear thoughts on use cases I might’ve missed.

Comments (3)

raelmiu · 34m ago
I have this problem every day. Worked fine with zoom, but never Teams. No idea why.
roughike · 2h ago
I only have one meeting a month nowadays so I might take a look if that situation ever changes (hopefully it doesn't!).

Regardless, congrats on the launch.

> the macOS app and Chrome extension communicate via WebSockets on localhost; nothing leaves your machine.

So the macOS app sets up a local webserver on some port that the Chrome extensions knows about in advance? Smart, kinda like how I had to do an auth flow for one of my CLI apps.

visualstackk · 2h ago
> I only have one meeting a month nowadays so I might take a look if that situation ever changes (hopefully it doesn't!).

I'm happy for you

> So the macOS app sets up a local webserver on some port that the Chrome extensions knows about in advance? Smart, kinda like how I had to do an auth flow for one of my CLI apps.

Exactly like this! Some caveats there since Chrome actually shuts down extensions after 30 seconds or so if nothing happens (so you need to keep firing off messages across the connection to keep the extension alive).