An AI assistant for Google Meet with no extension to install
Meet runs in a browser tab, and browser tabs are where assistant extensions usually live — inside the page, subject to whatever the page and the profile allow. Whisperer sits outside the browser entirely and hears the tab the same way your speakers do.
Any Google account · no extension, no add-on
- Bound to one browser and one profile
- Reads what the page exposes, and no more
- Stops at the edge of the tab: your other windows are invisible to it
- Managed profiles can block it outright
- Independent of browser and profile
- Hears the call as audio, not as page markup
- Can read anything on your screen when you ask it to
- Nothing to approve in the browser or the domain
Setup
The tab is not special
Whisperer does not know that Meet is Meet. It knows that an application is playing a human voice, which is all it needs.
-
Allow the microphone
Your side of the conversation. The browser will ask separately for its own microphone access — the two are unrelated and both are needed.
-
Allow system audio
On macOS, the Screen Recording permission — that is the route to other applications' sound, including a browser tab. On Windows, nothing extra, as long as the browser plays through the default output device.
-
Press play, then join
Start the session before opening the Meet link, and watch for both speaker labels in the first few lines of transcript.
Where it helps
Meet calls tend to be the mixed ones
Meet links get sent to people outside the organisation more often than a Teams channel does: clients, candidates, partners in other countries. Two features carry most of the weight there.
Limits
Two constraints, same as everywhere
-
First
One recording at a time, not an archive migration
A finished recording can be uploaded: the Meetings section takes one file up to 25 MB — mp3, m4a, wav, ogg, flac, aac, plus mp4 and webm, from which the audio track is used. What is missing is bulk upload of a whole archive; and it spends the same minutes a live call does.
-
Second
The audio has to reach your machine
If you dial into a Meet from a phone and keep the laptop silent, there is nothing for system audio to capture. The call has to be playing on the computer running Whisperer.
Questions
Google Meet questions
Do I need a Google Workspace plan?
No. Whisperer never talks to Google, so it behaves identically on a personal Google account and on a corporate one. Nothing about your Meet plan changes what you get.
Is there a Chrome extension?
No, and deliberately not. An extension can only reach what the tab gives it; a desktop application can hear the call and also read whatever else is on your screen when you ask.
Does my organisation have to allow anything?
Not for Meet's sake. Whisperer installs nothing into Google Workspace and requests no scopes on your Google account. Whether your workplace has its own policy about assistants on calls is a separate matter.
Will other participants know?
Nothing joins the call and no indicator appears. Telling them is a choice, not a technical requirement — and on an external call it is often the easier choice.
Does it work with Meet in Safari or Firefox?
Yes. The browser is irrelevant: Whisperer captures audio at the operating system level rather than through the browser.
One external call is the real test
Take the next Meet with someone outside your company — the kind you would have written up afterwards anyway — and compare the write-up you get with the one you would have made.