AI Note Takers That Don’t Join the Meeting
8 capture paths, one for each of the 8 vendors here. Each row carries the verification date of the record it is built from: 2026-09-07 and 2026-09-09.
“Doesn’t join the meeting” and “nobody knows it’s running” are two different things, and every vendor blurs them. This page keeps them apart, because the second one is what buyers are actually asking about and it is the one no comparison site answers.
Three mechanisms, one marketing phrase
The app records what your machine hears. Granola, Jamie, Krisp, Noota’s desktop path, Notta Desktop and tl;dv’s desktop app. Fails on device permissions, audio-device selection and OS versions.
The extension reads the platform’s own caption stream. Tactiq, and Noota’s extension path. Fails when captions are off, when you leave the tab, and for anything said before capture started.
The vendor is authorised by the platform rather than joining as a guest. Fireflies’ Google Meet SDK path. Fails on the platform’s own API limits - three active participants, no captions, no chat.
No bot does not mean no disclosure, and it does not mean no trace
“automatically posts a short message in the chat so all participants know AI note-taking is active”
help.tactiq.io/en/articles/9535734-how-to-use-tactiq-with-google-meet · verified 2026-09-09
“Noota does not automatically notify other meeting participants”
support.noota.io/en/articles/8564869-do-other-participants-receive-notification-when-i-start-recording · verified 2026-09-09
“there's no built-in Zoom announcement to trigger.”
www.granola.ai/blog/how-to-use-granola-with-zoom · verified 2026-09-07
Tactiq is bot-free and still announces itself in the chat. Noota’s extension and desktop paths do the opposite, and Noota’s own support page confirms it. That puts the entire consent burden on the user, and Noota’s documentation tells users to inform participants and comply with local recording law and GDPR. Noota is the tool whose team edits this site; this is its weakness stated in the same words we would use for anyone else.
Granola’s Zoom page draws out the consequence for a regulated buyer: with no platform recording, there is no platform announcement. If your consent mechanism is “Zoom told them”, bot-free capture removes it.
Mechanism, disclosure, OS floor and failure mode
| Tool | Mechanism | Is the other side of the call told? | OS floor as published | Published failure mode |
|---|---|---|---|---|
| Granola verified 2026-09-07 and 2026-09-09 | Local system-audio capture on the device | No. Granola's Zoom page states there is "no built-in Zoom announcement to trigger", because the platform is not recording. | Contradictory: "macOS 13 or above" on the Meet page, "Granola requires a minimum macOS 14 to run" in the setup guide. Windows supported. | No video and no retained audio: "Granola transcribes but doesn't capture video. Granola doesn't record your screen or save audio files." If the transcript is wrong there is nothing to re-review. It also "cannot isolate audio from individual applications", so anything else playing on the machine lands in the recording. |
| Jamie verified 2026-09-09 | Local device capture, no bot by design | Not published by the vendor. | macOS 13.1 or higher is published; no Windows minimum version is published. Jamie publishes no Google Meet documentation at all, so no Meet-specific requirement is published either. | Capture is bound to the device Jamie is installed on: "Jamie can only be used on your macOS or Windows device", and "Jamie will use your default microphone automatically" - whether system audio rather than only the microphone is captured is not published. Its docs also warn that "Very short recordings may not generate useful summaries." |
| Krisp verified 2026-09-09 | Virtual microphone and speaker devices on the local machine | Not published by the vendor. | macOS 14 Sonoma or higher; Windows 10 1903+ or Windows 11 | The speaker-device trap: "If Krisp Speaker isn't set up with your calling app, only your speech will be transcribed, and not the speeches of other participants." No error, no warning, a one-sided transcript. On Safari the speaker device cannot be changed at all. Krisp's AI Meeting Assistant FAQ also states audio is "either transcribed entirely on device or sent to our servers for transcription and then immediately deleted", which does not match the unqualified on-device framing of its product page. |
| Noota (extension and desktop paths) verified 2026-09-09 | Browser extension or desktop capture on the user's own device | No. Noota's support page states it "does not automatically notify other meeting participants". | Not published by the vendor | No recording notification is sent to participants at all on the extension and desktop paths: Noota's own support page states it "does not automatically notify other meeting participants". Nothing in the meeting signals that capture is running, so the entire consent burden falls on the user. |
| Notta Desktop verified 2026-09-07 | Local system-audio capture on the device | Not published by the vendor. | macOS 13 or later for system audio; macOS 11-12 is microphone only. Windows supported. | On macOS 11 and 12, "Microphone only - System audio recording is not supported": it records your own voice and not the other participants. On supported versions, "System audio captures all sounds played on your computer-not just meeting audio, but also music, notifications, and other sounds." |
| tl;dv desktop app verified 2026-09-07 | Local system-audio capture on the device | Not published by the vendor. | Not published by the vendor | tl;dv publishes no minimum OS version for the desktop app anywhere on its own site - only separate Mac (M-series), Mac (Intel) and Windows builds - so a buyer cannot check fleet compatibility from vendor sources before committing. |
| Tactiq verified 2026-09-09 | Browser extension reading the platform's own caption stream | Yes. It "automatically posts a short message in the chat so all participants know AI note-taking is active". | Desktop Chrome or Edge; no OS version published. | Capture depends on captions and on presence: "Tactiq can only capture speech after live captions are enabled. Speech from earlier in the meeting cannot be recovered if it wasn't transcribed." Leaving the call stops capture, and "Tactiq cannot retroactively change the transcription language of a completed live transcript". |
| Fireflies.ai (Google Meet SDK) verified 2026-09-09 | Platform-SDK capture: the vendor is authorised by Google rather than joining as a guest | Not published by the vendor. | Server-side SDK path; no OS floor applies and none is published. | "The Google Meet SDK captures audio and video from up to three active participants at a time - this is a Google API limitation." And "The SDK currently doesn't support chat messages or captions - only live audio and video streams are recorded." Only one active integration is permitted per meeting session. |
Who bot-free suits, and who it does not
It suits you if you meet mostly with people outside your own organisation and cannot get their admin to admit a bot; if you work in an environment where guest join is off tenant-wide; or if you simply do not want a visible participant in client calls. Nothing needs to be approved by anyone, because nothing joins.
The case against, stated plainly: if you need an auditable record that a recording took place and that participants were notified, the bot is the feature, not the bug. Bot-free capture leaves nothing in the meeting itself. Add the published failure modes above - a one-sided Krisp transcript, a Granola recording with the audio discarded, a Notta Desktop capture that is microphone-only on older macOS, an unpublished OS floor at tl;dv and Jamie - and the trade is real, not theoretical.
Questions buyers ask first
Is an AI note taker that doesn't join the meeting invisible to the other participants?
Not necessarily, and this is the distinction buyers get wrong. Tactiq is bot-free and still "automatically posts a short message in the chat so all participants know AI note-taking is active" (https://help.tactiq.io/en/articles/9535734-how-to-use-tactiq-with-google-meet, read 2026-09-09). Noota's extension and desktop paths do the opposite: Noota's own support page states it "does not automatically notify other meeting participants" (https://support.noota.io/en/articles/8564869-do-other-participants-receive-notification-when-i-start-recording, read 2026-09-09). No bot and no disclosure are two separate properties.
What are the different kinds of no-bot recording?
Three, and they fail in completely different ways. Local system-audio capture on your device (Granola, Jamie, Krisp, Noota's desktop path, Notta Desktop, tl;dv's desktop app). Browser-extension capture that reads the platform's own caption stream (Tactiq, and Noota's extension path). And platform-SDK capture, where the vendor is authorised by the platform instead of joining as a guest (Fireflies' Google Meet SDK path). All three are marketed with the same words.
Does bot-free recording remove the platform's recording notice?
Yes. Granola states there is "no built-in Zoom announcement to trigger" (https://www.granola.ai/blog/how-to-use-granola-with-zoom, read 2026-09-07), because Zoom is not recording. If your organisation relies on the platform notice as the consent mechanism, bot-free capture removes it and the consent burden moves entirely to the person recording.
Which bot-free tool has the worst published failure mode?
Krisp: "If Krisp Speaker isn't set up with your calling app, only your speech will be transcribed, and not the speeches of other participants." (https://help.krisp.ai/hc/en-us/articles/8326933081116-AI-Meeting-Assistant-FAQ, read 2026-09-09) - a silent, one-sided transcript with no error shown. On Safari the speaker device cannot be changed at all.
When is a bot better than bot-free capture?
When you need an auditable record that a recording took place and that participants were told. A visible bot participant is exactly that record. Bot-free capture leaves no trace in the meeting itself, so the bot is the feature, not the bug.
Platform-by-platform detail is on the Google Meet, Microsoft Teams and Zoom guides, which share the same underlying records as this page. Where a vendor’s pages disagree with each other, that is catalogued on the vendor claim tracker.