Works With · Video conferencing

Transcribe Google Meet on Mac without bots

Botless Google Meet recording and on-device transcription across modern Mac browsers.

Verified IntegrationEvidence in codebase: main/meeting/meeting-detector.ts, main/meeting/system-audio.ts (as of 2026-10-03)macOS 14.2+, needs Screen & System Audio Recording permission

Integration capabilities

  • Detect active Google Meet calls inside Chrome, Brave, Arc, Safari, and Edge automatically
  • Record browser audio and microphone streams with zero external attendee bots
  • Generate on-device Whisper transcripts and save Markdown notes directly to your local vault

Google Meet is the primary collaboration hub for modern startups, product teams, design agencies, and educational institutions. Because it runs seamlessly in the web browser without requiring a bulky desktop client, millions of professionals rely on Meet for customer discovery interviews, design sprints, and daily team syncs.

However, recording and capturing notes from Google Meet presents steep challenges. Google’s native recording and AI note features are restricted to expensive Google Workspace enterprise tiers with Gemini add-ons ($20 to $30 per seat per month), and upload audio to Google cloud servers. Third-party meeting assistants rely on conspicuous virtual attendee bots that require host admission, clutter call rosters, and introduce privacy concerns.

Oyma offers a sovereign alternative for Mac users. Operating at the macOS system level, Oyma detects active Google Meet sessions across all major Mac browsers, captures incoming audio and your microphone silently without an attendee bot, transcribes speech 100% on-device using Whisper, and writes clean Markdown notes directly into your local vault.

The browser capture challenge: Why virtual bots fail

Because Google Meet runs inside web browser tabs rather than a single dedicated desktop binary, conventional AI meeting notetakers face unique hurdles:

  • Admission friction: Virtual attendee bots must be admitted to the Google Meet room by the call host. In external customer interviews or prospective client pitches, asking the host to admit an unverified bot creates an awkward, unprofessional first impression.
  • Enterprise guest policies: Many enterprise Google Workspace domains enforce strict security policies that forbid external bots or unauthenticated guest accounts from entering video calls.
  • Expensive enterprise add-ons: Google’s own AI meeting summaries require enterprise Workspace subscriptions and cloud Gemini add-on licenses, locking individual contributors and small teams behind expensive software tiers.
  • Cloud privacy risks: Transcripts generated by cloud services are processed on remote server farms, conflicting with strict client confidentiality agreements or sensitive product research protocols.

How Oyma integrates with Google Meet on macOS

Oyma resolves the browser capture problem by monitoring macOS audio pipelines rather than inspecting browser DOM contents or deploying remote bots:

┌────────────────────────────────────────────────────────────────────────┐
│                  GOOGLE MEET CAPTURE PIPELINE ON MACOS                 │
├────────────────────────────────────────────────────────────────────────┤
│ 1. Browser (Chrome, Arc, Brave, Safari) launches meet.google.com       │
│ 2. CoreAudio detector recognizes VoIP stream & displays banner         │
│ 3. User clicks [Record Meeting] (explicit confirmation)                │
│ 4. ScreenCaptureKit captures system audio + mic into local memory      │
│ 5. On-device Whisper transcribes speech on Apple Silicon Neural Engine │
│ 6. Formatted note writes directly to vault's meetings/ folder (.md)    │
└────────────────────────────────────────────────────────────────────────┘

1. Multi-browser meeting detection

Implemented in src/main/meeting/meeting-detector.ts, Oyma monitors CoreAudio device activity alongside active application signatures. When Google Chrome, Arc, Brave, Safari, or Microsoft Edge establishes a bidirectional VoIP audio stream associated with a Google Meet session, Oyma presents a subtle desktop banner:

Google Meet session detected.
[Record Meeting]   [Dismiss]

Detection is completely non-intrusive and occurs entirely on your device, ensuring that no recording happens without your explicit consent.

2. Botless ScreenCaptureKit audio pipeline

When you confirm recording, Oyma leverages Apple’s native ScreenCaptureKit framework:

  • It isolates system audio output, capturing the voices of your colleagues and clients with crystalline digital clarity.
  • It records your local microphone input simultaneously.
  • Because recording happens inside the macOS kernel, no bot enters the Google Meet room, no recording banners disrupt participants, and no external audio packets are transmitted across the web.

3. Local Whisper speech-to-text on Apple Silicon

When your Google Meet call concludes, Oyma processes the audio buffer using on-device OpenAI Whisper models optimized for Apple Silicon Neural Engine cores. With support for 13 languages and automatic language detection, transcription completes in minutes without consuming external API credits or uploading sensitive dialogue to cloud servers.

4. Structured Markdown output in your Obsidian vault

Meeting insights are instantly structured with YAML frontmatter, executive takeaways, action items, and timestamped transcripts, saved directly into your vault:

---
title: "Customer Discovery Interview: Fintech Workflow"
date: 2026-10-08
platform: Google Meet
attendees: ["Elena Rostova", "David Miller"]
tags: [customer-research, product, google-meet]
---

## Executive Summary
Interviewed head of operations regarding monthly financial reconciliation pain points. Core bottleneck is manual CSV manipulation across disjointed reporting tools.

## Key Insights
- Current reconciliation workflow takes 14 hours per week across 3 analysts
- Primary frustration: lack of audit trails when reconciling discrepancies
- Strong interest in local Markdown-compatible audit logs

## Follow-up Action Items
- [ ] David: Draft prototype workflow spec based on feedback
- [ ] Elena: Send anonymized sample reconciliation file by Thursday

Because notes are written as plain .md files, they integrate seamlessly with Obsidian, Raycast, Alfred, and local command-line search tools (ripgrep).

Ideal use cases for Google Meet on Oyma

  • Customer discovery & UX research: Conduct in-depth user interviews without the distraction of an attendee bot making research subjects self-conscious.
  • Sprint planning & agile retrospectives: Capture fast-paced engineering discussions and generate actionable checklist items without manual note-taking overhead.
  • Client consulting & advisory calls: Guarantee absolute data confidentiality for high-stakes strategic reviews where cloud transcription is strictly prohibited.
  • Candidate interviews: Maintain respectful, distraction-free hiring discussions while preserving an accurate, verbatim transcript for hiring committees.

Privacy you can audit: The Egress Log

Every outgoing network request in Oyma is recorded in the built-in Egress Log. You can inspect network activity at any time to verify that your Google Meet audio recordings, summaries, and notes remain 100% on your Mac.

Capture every Google Meet conversation with confidence, discretion, and complete local data sovereignty.

Does Oyma work if I run Google Meet inside Chrome or Arc?

Yes. Oyma monitors browser audio sessions and window signatures across Google Chrome, Arc, Brave, Safari, and Microsoft Edge, detecting when an active meet.google.com call launches.

Do other meeting participants see a recording bot in Google Meet?

No. Oyma records system output audio and microphone input via macOS ScreenCaptureKit. No virtual bot enters the Google Meet room, so other participants see only your standard video tile.

Do I need a Google Workspace Gemini add-on subscription?

No. Google charges $20 to $30 per user monthly for Gemini Workspace add-ons that generate cloud meeting notes. Oyma runs 100% locally on your Mac's Apple Silicon hardware for free during its private beta.

Where are Google Meet transcripts saved on my Mac?

Transcripts, action items, and summaries are saved directly into your local Markdown vault as standard .md files, fully compatible with Obsidian, VS Code, and any plain text editor.

Your meetings, in plain Markdown.

Free during the private beta. Apple silicon Macs, macOS 14 or later.

One email when your invite is ready. No newsletter.