Live answers in Google Meet
Meet is the one platform Cue is set up for out of the box: the extension declares it by name, so there is nothing to allow and nothing to configure. Open the call, click the icon, and the window is there.
Compatibility
Exactly where it runs.
No small print further down the page: this is the whole compatibility story for this platform.
Getting started
Three steps, once.
Join the call as usual
Nothing to change about how you get into the meeting, and nobody to invite. Cue is not a participant.
Click the Trippi Cue icon
That click is what hands the tab’s sound to the extension. Chrome allows no other way in, and we would not want one.
The window opens over the call
Drag it anywhere, resize it, close it. Meet keeps working underneath exactly as before.
In the call
What a card looks like here.
Google Meet
Trippi Cue
Heard in the call
So, Anna — how would you handle the migration window on your side?
Suggested answer
Over a weekend, with the old system readable for a week and a one-hour path back if anything looks wrong.
A mock-up, not a screenshot: real ones go here once the extension is in the store.
Your name in the question is one of the strongest signals the local filter has, but it is not required: “what would your side do here” gets picked up too, because the model sees who has been speaking and who has not.
How it differs
Cue and what Google Meet already has.
It is not built into Meet
Cue is your extension in your browser. It needs no Workspace licence, no admin approval and no change to how your organisation runs Meet.
It answers instead of transcribing
Meet can show captions of what is being said. Captions are a record of the question; a card is an answer to it.
Nothing appears for other people
No participant, no notification, no “recording” badge — the window lives in your tab only. Do note that it becomes visible to everyone if you share that tab.
When it misbehaves
Troubleshooting.
The window does not appear
Click the extension icon while the Meet tab is the active one. Without that click Chrome gives out no audio at all, so there is nothing for the window to show.
It says nothing is being heard
Check that the meeting audio is actually playing in this tab and that the tab is not muted. Cue hears the tab, not your microphone and not your room.
Cards stopped mid-call
Either the monthly minutes ran out — the window says so plainly — or the connection dropped. Clicking the icon again starts a fresh session.
Still stuck? Write to us — the message arrives with your version and platform already filled in.
Where the audio goes
From your browser straight to our speech-to-text provider over an encrypted connection. It does not pass through our servers, and it is never recorded. The recognised lines become one prompt for the model and are dropped with the answer.
Other platforms
FAQ
Google Meet, specifically.
Does it work in a Meet call started from Gmail or Calendar?+
Yes. However you get there, you end up on a meet.google.com call address, and that is what matters.
Will other people see the window if I share my screen?+
If you share that browser tab, yes — the window is part of the page. Share a different window, or close Cue before you present.
Does it need the Meet captions turned on?+
No. Cue listens to the sound of the tab, so it works whether or not Meet is showing captions.
Does it work in a breakout room?+
Yes — a breakout room is the same tab and the same call address, so the session carries on.
Your next Google Meet call, with the answer already on screen.
Trippi Cue is free in the Chrome Web Store. One click on the icon in the call, and the first ten minutes are on us.