Brief your AI from Google Meet, no extension
Capture Google Meet audio with Meeting mode on your Mac, then use a reviewed transcript or brief as context for your AI. No Eavesy browser extension or meeting participant bot is required; device and organization policies still apply.
How it works with Google Meet
- 1
Join your Google Meet call in the browser.
- 2
Press record in Eavesy to capture Meet audio and your mic.
- 3
On long Mac sessions, processed transcript and notes arrive in batches as sealed segments upload.
- 4
Stop to save a clean brief and full transcript you can paste into any agent.
Frequently asked
- Does this need a browser extension?
- No. Eavesy records system audio at the OS level, so it works with Google Meet in any browser without an extension.
- Can Eavesy join a Meet call for me?
- Yes, if you want it to. When you can’t record from your Mac, send the Eavesy Notetaker from the web app. It joins as a visible participant, and the transcript fills in during the call.
More video calls integrations
Use Meeting mode for both sides of a call
Open Eavesy with ⌘⇧Space and choose Meeting. It captures the microphone and audio played by your Mac without saving screen video. Choose Video only when the visual walkthrough is part of the evidence you want to retain.
Join the call in your usual browser. This workflow captures audio played by the Mac; it does not require an Eavesy extension inside the browser.
Grant the required macOS Microphone and Screen Recording or system-audio permissions. The fact that no Eavesy bot appears in the participant list does not remove consent, organization, or device-management requirements.
Verify a short sample before the full meeting
Record a few seconds of your voice and permitted computer audio, stop, and play it back. Both sources should be audible. If only one is present, check the input or playback route and permissions before repeating the test.
During a signed-in recording, sealed segments can upload and process in batches. The final transcript and brief may still be processing when you stop. On-device captions are preliminary text, not the finished cloud transcript.
Reuse the completed context
Review the transcript around decisions, names, and numbers. Eavesy can distinguish the microphone and remote-audio tracks as You and Them; that does not identify every remote speaker. Copy the relevant brief into an agent with a specific question, or use the hosted MCP connection for supported synced account content.
A useful follow-up request is “List agreed actions and quote the supporting passages. Leave owners and deadlines unknown when they were not assigned.” Check the original passage before forwarding the result.
What stays local
Local recordings remain normal files on your Mac. Signing in enables cloud audio processing and synced retrieval. Local standalone screenshots and notes do not become available through hosted MCP simply because they were captured around the same call.
Check the browser call and the recording separately
Join Meet in your normal browser and confirm you can hear the call through the intended output. Then test Eavesy Meeting mode with that same route. Browser access to your microphone and Eavesy’s macOS permissions are separate controls; one application’s successful capture does not establish the other’s access.
A useful post-call check is a passage you spoke followed by a passage from a remote participant. If playback contains both but the final text is pending, investigate processing. If playback lacks one side, investigate capture and routing.
Use the completed brief as a starting point for notes, then verify decisions and commitments against the transcript. The meeting-to-Markdown example shows how to preserve a useful decision while leaving missing ownership unresolved.
Capture it once. Use the context anywhere.
Capture on your Mac and keep normal files. Sign in for cloud transcripts and briefs, then share the context your AI needs.