sync mic mute/unmute with google meet

[ComputelessComputer]

when you mute your mic in g-meet, it implies that you do NOT want to have your voice being transcribed.

[lukewma-aws]

the pre v1 (v 0.83) versions had an ui option to disable the local mic only, or select the mic interface (bluetooth, mac, etc). Is there a plan to bring that back?

[yujonglee]

Hi @lukewma-aws can you add more color on that? What is your use-case & thought process?

• We removed mic/speaker mute because it is very rare that user want speaker mute. Also mic mute is ideally synced with Zoom etc, so no need explicit control in Hyprnote
• It seems like it is better to follow "default input device", and let other tools(in the future Hyprnote will have option too) set what should be default. See also support audio interfaces #1258 (comment)

[lukewma-aws]

@yujonglee I used speaker mute to disable the default connection to my bluetooth mic when having in person meetings, but I can work around that. However, for mic mute, mine did not sync with zoom, so thats why i needed explicit control.

[yujonglee]

@lukewma-aws Zoom mute syncing should work if you give Hyprnote accessibility permission.

---

Screen.Recording.2026-01-08.at.1.38.11.PM.mov

[yujonglee]

@ComputelessComputer and others waiting for Google Meet Sync

Google Meet sync is significantly harder than Zoom - roughly 3x the complexity.

**Why Zoom is easy:** It's a native macOS app with a standard menu bar. The current implementation uses ~50 lines of AppleScript to check if "Mute audio" or "Unmute audio" menu items exist.

**Why Google Meet is hard:** It runs in a browser with no native menu bar. The mute button is inside the DOM, and critically, Google Meet keeps the mic stream *active* even when soft-muted (to show "you're talking while muted" warnings), so audio monitoring won't work.

**Recommended approach: Browser Extension**
- Create a Chrome extension that monitors the mute button's `aria-label` via MutationObserver
- Communicate with Hyprnote via Native Messaging or local WebSocket
- Effort: ~200 lines JS for extension + ~100 lines Rust for native messaging
- Downside: Users must install the extension

**Why other approaches don't work well:**
- Accessibility API: Browser AX trees are massive, slow to query, and Meet's DOM structure changes frequently
- Audio monitoring: Can't distinguish muted vs. silent user (mic stays "in use" when muted)
- AppleScript JS injection: Disabled by default in Chrome

The extension approach is how tools like Elgato Stream Deck handle Google Meet integration. It's the only reliable way to detect "soft mute" in a web app.

lmk if there's better approach

[yujonglee]

I think using Chrome extension is way to go