No meeting bot
Nobody new appears in the participant list
How a bot ends up in your meeting
Most AI meeting tools work the same way. You connect a calendar, and at the appointed minute a service dials into the call as a guest. It arrives in the participant list with a name. Somebody has to let it in. The platform announces it, the chat usually gets a line, and several products send an email to everyone on the invitation beforehand asking whether anyone objects — with an opt-out that keeps the bot out if a single person declines.
That is not sloppiness in those products. It is the honest cost of what they do, which is record the call and produce a file afterwards. A recording needs consent, consent needs an announcement, and an announcement needs something in the room to announce.
Cue does none of that, because it does none of that. There is no recording, so there is nothing to declare, and no guest, so there is nobody to admit.
Where Cue sits instead
It is an extension in your own browser
Added from the Chrome Web Store, running in Chrome on your machine. We operate no service that dials into anything. There is no account of ours with a seat in your meeting, and no infrastructure on our side that could ask for one.
It hears the tab, not the room
Click the icon in the tab your interview is in, and Chrome hands that one tab’s audio to the extension — the sound the call is already playing back to you. Your microphone is never requested. Neither is any other tab.
The window is drawn in the page
Cards appear in a small window inside the meeting page, in its own shadow tree: the call’s styles cannot reach it and its styles cannot reach the call. It is part of your browser, not part of the conference.
Only a real click starts it
Chrome gives tab audio to an extension only after you click its icon in that tab. There is no autostart to configure and no scheduled job that could begin without you — not even one we could add later.
The list of things that therefore do not happen
Why the platforms started caring about this
During 2026 both Google Meet and Microsoft Teams changed how they treat third-party note-taker bots: Meet surfaces unfamiliar ones as a potential risk, and Teams routes them into a suspected-threats lobby rather than straight into the call. Meanwhile Google’s own built-in note-taking puts a pencil icon and a banner in front of every participant, and that notice cannot be switched off.
Read one way this is a privacy story. Read another way it is a reliability story, and the second one is the point here. A tool that has to be admitted depends on a decision somebody else makes every single time — a host setting, a lobby policy, an admin rule. An extension that never attempts to join is not on the wrong side of that change. It is not in that argument at all.
What this boundary costs you
Browser calls only
Google Meet, Zoom on the web, Microsoft Teams on the web. If your interview is booked into the Zoom or Teams desktop client, an extension cannot hear it — ask for a browser link, or join from the browser yourself.
One tab, sound only
The tab you started it in, and nothing else. Not your microphone, not your screen, not the rest of your browsing. A bot in the call hears the room; Cue hears what the call plays back to you.
No artefact afterwards
No recording, no summary, no notes, no action items. Cue is not a note-taker that skips the bot — it is a different product that answers the question asked of you while the call is running.
Gone when you close it
Closing the window pauses the session. Removing the extension ends it entirely: no background service, no startup item, nothing left on the machine to stop.
What does leave the tab
“No bot” is not the same as “nothing leaves your computer”, and it would be dishonest to let the first imply the second. The sound of the tab goes from your browser straight to the recognition service over a temporary session token, without passing through our servers, and is not stored anywhere. What reaches us is text: a window of the last twelve recognised lines, the participant names, your name, and whatever you typed into the brief. That goes on to the language model that writes the card.
That window and the answer are kept for 30 days — long enough to tell a poor answer from a poor question — and are then deleted automatically. The audio is never stored at all, because it never arrives. There are no documents in the picture, because Cue cannot read any.
Not joining is not the same as not being noticed
This page is about one narrow, checkable fact: no participant is added to your call. It is not a claim about what the person on the other side of the call can work out. A window drawn in your browser page is on show the moment you share that page, a pause before an answer is audible to anyone listening, and the rules for a given interview are set by the person running it, not by us.
We would rather say that here than let a true statement do the work of a false one.
FAQ
The uncomfortable questions.
Does Trippi Cue join the meeting as a participant?+
No. Cue is a Chrome extension running in your own browser, not a service that dials into calls. Nothing connects to the meeting as a client, so the participant list gains no entry, the host is never asked to admit anything, and no “joined the meeting” line appears in the chat.
How can it hear the call without being in it?+
It listens to the tab. After you click the extension icon in the tab your interview is running in, Chrome hands that tab’s audio to Cue — the same sound the call is already playing back to you through your speakers. Your microphone is never requested, and no other tab is touched.
Does it connect to my calendar or send anything to the other participants?+
Neither. Cue has no calendar access at all, so it cannot read your events or add an attendee to one, and it sends no email or chat message to anybody. Bot-based note-takers do send those notices on purpose, because something of theirs is about to attend. Nothing of ours attends.
Is the call recorded?+
No. There is no audio file, no video and no transcript to download, and the platform’s own recording indicator stays off because Cue does not start a recording. What is kept on our side is text — a window of the last twelve recognised lines, the participant names and the answer — for 30 days, after which it is deleted automatically.
Will the host’s bot settings or a locked meeting stop it working?+
No, and for the same reason as everything else here: those settings decide what may join a call, and Cue never asks to join one. Its limits are different ones — it works in Google Meet, Zoom on the web and Teams on the web, and cannot help at all in the Zoom or Teams desktop clients.
If nobody is told, is it fine to use?+
That is a separate question from this page, and we do not treat it as settled. Nothing joins your call and nothing is recorded, so there is no recording for anyone to consent to — but many interviews and assessments state plainly that outside help is not allowed, and Cue is outside help. Which rules apply to your call is something only you can know; our position is set out on the responsible use page.
Add it before the next call, and watch the participant list stay the same.
Trippi Cue is in the Chrome Web Store. One click on the icon when the call begins, and nothing before that.