No-bot

Record Google Meet Without a Bot | Reline

Record your Google Meet — no bot in the participant list, no awkward "has joined the meeting."

Reline Team June 1, 2026

Most AI notetakers record a Google Meet by sending a bot into the call. It shows up in the participant tray, your guests see "Notetaker has joined," and you spend the first two minutes explaining what it is. There is a quieter way: record the meeting from your own computer, the same way you would screen-record your laptop, with nothing joining the call. This guide covers why the bot is a problem, how local capture actually works, the exact steps to record a Meet with Reline, and an honest breakdown of what is local and what is not. No magic claims — just the mechanism, the trade-offs, and the consent reminder you should not skip.

Why a bot in your Meet is a problem

A bot is a visible, third-party participant in a conversation you do not control. Three concrete costs follow. First, optics: when "Otter has joined the meeting" pops into the tray, that is your guest's first impression, and it is a vote that you brought a stranger into their call. Second, consent friction: a bot in the list forces an explanation up front, and on sensitive calls people clam up the moment they see a recorder named after a SaaS vendor. Third, IT blocks: plenty of Google Workspace tenants restrict or outright deny third-party apps from joining meetings, so the bot silently fails to admit, or an admin blocks it after one complaint. None of these are dramatic on a casual standup. All of them compound on the calls that actually matter — sales, hiring, anything regulated. Removing the bot removes all three at once.

How bot-free recording actually works

Bot-free recording does not connect to Google Meet at all. Instead it captures two audio streams directly from the computer you are already using to attend the call. The first is your microphone — your voice. The second is system audio: everything coming out of your speakers, which includes every other participant in the Meet. Your operating system exposes this through a documented API (ScreenCaptureKit on macOS, WASAPI loopback on Windows, the equivalent on Linux), gated behind a one-time permission grant. Because the capture happens on your machine, there is nothing to admit into the call and no participant for anyone to see. From Google's point of view you are just a normal attendee with your speakers on. The recording is yours, the way a local screen recording is yours. To see the full picture of what bot-free does and does not mean, read the deeper explainer at /no-bot.

Step-by-step: record a Google Meet with Reline

  1. Open the Reline desktop app before your call (macOS, Windows, or Linux). The first time, grant the screen/system-audio and microphone permissions when prompted — this is a one-time step.
  2. Join your Google Meet the way you always do, in your browser or the Meet app. Reline does not need a link, a calendar invite, or a bot to admit. On macOS, Reline can auto-detect that a meeting started and offer to record.
  3. Hit record in Reline. It captures your mic and the meeting's system audio locally and starts streaming a live transcript as people talk.
  4. Talk normally. Nothing appears in the Meet participant list and no recording banner is pushed through Google. When the call ends, stop the recording and Reline turns it into a transcript, summary, and replayable timeline.

That is the whole flow. No bot to invite, no admin approval, no "waiting to be admitted." See the full feature set at /product.

Honest note on privacy: capture is local, processing is cloud

We are deliberate about this because the category is full of overclaims. The capture step is local: your mic and system audio are recorded on your own machine, and no bot joins the Meet. That is the part people care about for the participant-list problem, and it is genuinely local. But the rest is not. The recorded audio is sent to a cloud transcription provider to be turned into text. It is stored in cloud object storage (Cloudflare R2). The AI summaries and chat run in the cloud. So we will never tell you "your audio never leaves your device" or that we do "on-device AI" — that would be false. If your requirement is that audio physically never leaves the machine, no cloud notetaker, including Reline, meets it. If your requirement is "nothing joins my Google Meet," bot-free capture meets it exactly.

What you get after the call

Once the Meet ends you do not just get a wall of text. You get a live transcript in 60+ languages, with automatic language detection — it was already streaming during the call, with speaker labels split as "Me vs Other" — Reline tells your microphone apart from the meeting's system audio rather than naming each person, since there is no participant grid to read from. You get a summary whose claims are citation-backed: every point links to the transcript moment that justifies it, so you can verify instead of trusting. And you get real playback — a timeline scrubber, click-any-line-of-transcript-to-seek to that audio, and per-speaker isolation. That playback layer is the part bot-only tools usually skip, and it is why a misheard number or a half-remembered commitment is something you can actually go re-listen to in two clicks.

Consent and the law: tell people you are recording

Removing the bot removes the automatic banner, which makes it more important, not less, to say something. This is not legal advice, but the practical reframe is simple. Some US states (and some countries) are one-party consent — you, as a participant, can record. Others are two-party (really all-party) consent, where everyone on the call must agree. Reline does not push a recording notification through Google Meet and does not add a visible participant, so the disclosure is on you. The good habit, regardless of jurisdiction: open the call with "I'm recording this so I can focus on the conversation — let me know if that's a problem." Most people appreciate the heads-up, and it keeps you on the right side of whichever consent rule applies. When in doubt, disclose and, for regulated work, check with counsel.

Reline vs bot-based notetakers

The clean dividing line is whether the tool joins your Meet. For virtual calls like Google Meet, Otter's notetaker joins as a visible bot participant — useful if you want to send it to a call you cannot attend, but it means a recorder is in the tray (Otter does also offer bot-free capture on its mobile and desktop apps for in-person audio). Reline takes the other path for virtual calls: it captures locally and never joins. Bot-free capture itself is not unique — tools like Granola and Krisp also record locally. Where Reline differs is reach and depth: Granola is Mac, Windows, and iOS with no Linux or web app, while Reline covers macOS, Windows, Linux, and web. On top of that you get the replayable timeline, citation-grounded chat over your notes, and private-by-default five-level team permissions so a recording is not just a personal file. See the head-to-head at /vs/otter.

Pricing is straightforward: Free at $0, Professional at $15/month ($140/year, about $12/month), and Enterprise at $32/month (about $26/month annual). The full breakdown lives at /pricing.

Reline is a desktop app for macOS, Windows, and Linux, plus a web app — no mobile app today. Download it, join your next Google Meet normally, and hit record.

FAQ

Common questions

Does Reline join my Google Meet as a bot?
No. Reline never joins your call as a participant and never appears in the attendee list. It runs on your computer and records your microphone plus the meeting’s system audio locally, so there is no bot to admit or notify.
Will other people see that I’m recording?
Reline does not add a visible participant or send a recording-started notification through Google Meet. You should still tell participants you are recording, since consent laws vary by jurisdiction.
Is my Google Meet audio processed on my device?
Only the capture step is local. The recorded audio is sent to Reline’s cloud transcription provider and stored in cloud storage, and AI summaries run in the cloud. Reline does not do on-device transcription, so we don’t claim audio never leaves your device.
What languages does the transcript support?
Transcription covers 60+ languages, with automatic language detection, so you get an accurate transcript whatever language the meeting is in.
Does it work on Linux?
Yes. Reline ships a desktop app for macOS, Windows, and Linux, plus a web app. There is no mobile app.
How is this different from Otter?
For virtual calls like Google Meet, Otter’s notetaker joins as a visible bot participant. Reline captures audio locally and never joins the meeting. Otter does also offer bot-free capture on its mobile and desktop apps for in-person audio.

Ready when you are

Stop taking notes.
Start shipping outcomes.

Free to try. Five minutes to install. Your first transcript is already waiting.