Skip to content

Docs

Google Meet

A PersistMemory panel inside the call. Ask what you already told it, keep what was just decided, and — when you choose to — put an answer where everyone can see it.

Adding it

In a call, open Meeting tools from the bottom right, choose the Add-ons tab, and pick PersistMemory. It opens in the side panel, which only you can see.

The first time, it asks you to sign in with Google. If you already have a PersistMemory account with that address, the panel connects to it; if the address is not verified on both sides, it will send you to the website once rather than link the two automatically — see Signing in below for why.

What it can do

  • Ask. The same answers you get anywhere else, from the same memory. Follow-up questions stay in the conversation, so “what about the other one” means something.
  • Remember. Type what was decided and keep it. It goes through the same pipeline as everything else, so it is extracted, resolved against what you already know, and searchable from every other surface.
  • Share. Put the last answer on the main stage, where the whole call sees it. Nothing reaches that frame unless you press the button.

What it cannot do, and why

It does not hear the meeting. A Meet add-on runs in a sandboxed frame with no access to audio, video, or the participant list. Google gives it two things about the call — the meeting id and the meeting code — and nothing else.

So there is no recording, no transcript and no note-taking here. What the panel knows is what you type into it.

Signing in

The panel uses Google One Tap, because a frame inside Meet cannot navigate you anywhere. If your browser blocks third-party cookies the prompt will not appear at all — that is a Google limitation, not a fault — so the panel falls back to a normal Sign in with Google button.

The panel holds a fifteen-minute access token, in memory only. It is never written to browser storage, and no long-lived refresh token is issued to it — a credential that outlived the call would be a credential sitting in a frame you do not control.

An account is never linked to a Google identity unless both sides have the address verified. Otherwise anyone able to create a Google account claiming your address would be handed the matching PersistMemory account.

The shared stage

The main stage is rendered to every participant. It never signs in and never reads your memory: it displays only the text you sent to it by pressing Share. That is enforced in the code, not by convention — the shared frame makes no API call at all.

Other ways in: Telegram, MCP, and the command line.