krystiangw/meet-live-assist-extension

**Your own agent session, in the call with you.** It reads the Meet or Zoom transcript as it happens and
answers in a side panel while the call is still going: what was decided, who owns what, the risk you just
agreed to, and the sentence to say next, in the meeting's language.
A release review, fourteen seconds, panel docked beside the call. The conversation is invented and the
cameras are off, as they are on most working calls. The interface is the shipping one.
**Install from the Chrome Web Store** · **the site** ·
one command for the server: npx meet-live-assist-server
The store link is one click and updates itself; the repo works loaded unpacked and never does. Either way
the server and the skill below are still yours to run, and without an agent attached the advice pane stays
empty by design.
During a Google Meet or Zoom call this captures the transcript, shows it in a side panel, and hands it to
an assistant running on your own computer. The assistant answers back in the panel while the call is still
going: what to say, what was decided, who owns what, what you just agreed to that you should not have.
Transcripts, screenshots and chat are written to a folder on your disk and served by a server on
127.0.0.1 that only you can reach. There is no account, no telemetry, and no server of ours anywhere.
**Where the words actually go, stated once and plainly.** The brain is your own Claude Code session, so
whatever you route to it - the transcript batches, your questions - leaves your machine for Anthropic under
*your* account, exactly as any other Claude Code session does. What never leaves is the stored record: the
files, the screenshots, the chat history. If a page tells you a live meeting assistant runs entirely on your
machine, it is either using a local model or it is not telling you the truth; this one borrows a brain you
already pay for, and that is the trade. See Data flow for the three-line version.
Read this before you install
**You need an AI coding agent that speaks MCP - Claude Code is the one
this is tested with.** This ships the eyes, ears and hands - the capture, the panel, the local bridge - but
not the brain. The brain is an agent session on your own machine, reading the call through MCP tools. Without
one you get a working transcript recorder and an empty advice pane, which is not what the screenshots promise.
The adapter is plain JSON-RPC over stdio with nothing vendor-specific in it, so other MCP clients (Cursor,
Cline, Continue, Zed, Codex) can drive it - Codex CLI was checked and completes tool calls against the bridge.
One requirement is genuinely harder to meet elsewhere: the client has to hold a **persistent background
loop**, because MCP is client-pull and nothing on the server can
ever start a turn. MCP-CLIENTS.md explains what to check and what is unverified.
**Your meeting is other people's conversation too.** Turning on captions is invisible to everyone else,
unlike recording, which Meet badges. So by default this posts one line into the meeting chat when capture
starts, saying an assistant is transcribing locally. You can edit that line or turn it off in Options.
Some jurisdictions require everyone's consent before a conversation may be recorded or transcribed; that
is your call to make, and PRIVACY.md says so plainly.
Requirements: Node 20+, Chrome 116+, Claude Code. Speaking *into* the call is macOS-only (it uses say
and afplay); elsewhere advice still appears in the panel and the server says why it cannot speak. Local
speech-to-text works anywhere ffmpeg and whisper.cpp do, and the panel's setup row names which of the
two is missing instead of failing quietly.
Install (three steps)
Then:
1. **Start the bridge server**, leave it running:
node server/transcript-server.js --pair
2. **Load the extension**: chrome://extensions → Developer mode → *Load unpacked* → pick this folder.
Pin it, click the icon. The panel collects its token from the pairing window on its own; there is
nothing to copy. (Window expired? Run step 1's command again - it works against a running server too.)
3. **Open Claude Code** and ask it to assist your meeting.
./install.sh takes MLA_USER, MLA_LANGUAGE, MLA_DOMAIN and MLA_TRANSCRIPTS_DIR so the assistant
addresses you by name, in your language, and knows roughly what your meetings are about.
Pick a profile
MLA_PROFILE decides which meeting types the assistant knows about and what it leads with. Everything else -
the markers, the modes, the board - is the same, because those turned out to be domain-neutral.