Can I use an AI notetaker if I'm not the meeting host?

Yes — but the answer splits by tool type, because the host controls the meeting platform and you don’t. Anything that has to be switched on inside the call is theirs to allow; anything running on your own computer isn’t.

What “host” actually gates

Being the host isn’t a courtesy title — on every major platform it’s the permission boundary for capture. The host, or an admin in the host’s organization, generally decides:

• whether the meeting can be recorded at all, and who may press Record;
• whether the platform’s built-in AI runs, and whether a transcript is produced;
• whether guests from outside the organization get admitted, and out of what lobby or waiting room;
• in some configurations, whether live captions are available.

Join a call you didn’t create and every one of those is decided for you before you arrive. (Settings names and defaults move between releases, and admins can lock them, so treat the specifics below as the shape of the rule rather than a fixed menu path.)

The five options, by whether the host can stop them

1. The platform’s own AI — host-gated, and usually out of reach. Zoom AI Companion is started on the host’s account; Teams’ Copilot recap depends on the meeting being transcribed and on your own license; Google Meet’s note-taking is tied to the host organization’s Workspace edition. As a guest on another company’s call, you generally won’t even see the control. This is the sharpest version of a limit covered in Canary vs Zoom AI Companion and Canary vs Google Meet.

2. Recording — host-granted by design. Participants can usually be given local-recording rights by the host, and cloud recording stays with the host or a co-host. If Record is greyed out for you, that’s the intended behaviour, not a bug.

3. A notetaker bot — admitted or refused at the door. A meeting bot joins through the link like any guest, which means the waiting room, the lobby, and external-participant restrictions all apply to it. Hosts increasingly keep them out on purpose. A bot also needs the meeting link in advance, so ad-hoc calls you were pulled into often miss it entirely.

4. A caption-scraping browser extension — partly gated. These read the live captions the platform is already drawing, so they need captions to be running and the meeting to be in a browser tab. Some platforms let the host disable captions for everyone, and desktop-app users are out of scope regardless.

5. Capturing your own computer’s audio — not host-gated at all. System-audio capture reads the sound your machine is already playing: the other participants’ voices, exactly as they reached your speakers. It never authenticates to Zoom, Teams, or Meet, never asks to be admitted, and adds nothing to the participant list — so your role in the meeting simply isn’t part of the equation. It works the same in a call you host, a call you were invited to, and a call you joined from a link someone pasted into Slack two minutes ago.

Why this lands hardest on guests

If you host most of your meetings, this whole question is academic — turn on the platform’s AI and you’re done, at no extra cost on a paid plan. The problem belongs to people who spend their day inside other people’s meetings: consultants and agencies, vendors and partners on client calls, candidates and interviewers across org boundaries, and anyone in a company whose customers all use a different platform. For them, the tool that worked yesterday depends on today’s host — which is not a workflow so much as a coin flip.

Note the honest trade in the other direction: a bot can attend a meeting you skip entirely, and platform AI is the option your client’s security team already approved. Neither of those is something a desktop tool replicates.

What Canary does

Canary is a real-time, bot-free meeting summarizer. It captures your computer’s system audio (no bot in the call, no plugin, no virtual audio device) and shows a live, multi-resolution rolling summary — from what’s being said right now to the whole call — so you can catch up the instant your name is called. Because it listens to your own machine rather than the meeting service, being a guest changes nothing about how it works, and it behaves identically across Zoom, Meet, Teams, or anything else playing audio on your computer. It runs on macOS, Windows, and Linux.

That also means the summary arrives during the call rather than after it — see can I get a live summary during a Zoom call. If your blocker is an organizational bot ban rather than the host’s settings, can I use an AI notetaker if my company blocks meeting bots covers that separately.

Not host-gated is not the same as permitted

This is the part worth being straight about. That the host’s controls don’t reach your laptop is a fact about software architecture, not a permission slip:

• Tell people. One sentence at the top of the call — “I’m running an AI notetaker that summarizes for me” — costs nothing and settles it. See how to tell participants you’re using an AI notetaker.
• A “no” is a no. If the host has declined recording, or the meeting was called on the understanding that it isn’t captured, reaching for a different capture method to get around that answer is the wrong move. Ask instead; on internal calls you’ll usually get a yes.
• Consent law doesn’t care who hosts. Some regions require only one participant’s consent, others everyone’s — see one-party vs two-party consent. Your role in the meeting has no bearing on which rule applies.
• Their confidentiality expectations still cover the conversation. On a client or partner call, the other organization’s rules are part of the deal even though their admin can’t enforce them on your device.

Not needing the host’s permission button is a statement about how the capture works. Whether you should be capturing the meeting is still a conversation to have out loud.