Running one.
Everyone else in the room just talks. This page is for you, in the order you'll actually need it.
What you need before you start
MachinemacOS, Apple Silicon. Windows installs but does not start the agent; Linux is partial.
AgentYour own Claude subscription. The app runs your Claude Code — it stores no key of its own.
MeetingGoogle Meet. Slack huddles are partial — joining and speaking are not wired.
VoiceOptional ElevenLabs key. Without one it uses the built-in system voice.
Shared boardRequires signing in to the service, because the board is hosted and shared from there.
The path
- Install the app and restart your terminal agent once. The tools only appear in a session started after the install.
- Give the bot a name and a voice before its first call. This is not cosmetic. The two frictions at first contact are that it arrives unnamed and sounds like nobody. A named agent gets treated as a participant — that has been the hinge in every call that went well.
- Open a Meet, then tell your agent to join it. It asks to join; you admit it. The name it joins under is fixed for the whole call.
- Turn captions on and confirm it can hear. This is the step people skip and the reason most bad calls were bad. Ask it something and check that it answers the question you asked.
- Set the mode out loud. In a room with people who didn't ask for it, keep it quiet until named, and tell the room that's what it's doing. The predictability is what makes people relax.
- Give it something to make. Not a question to answer — a thing to build on the board while you keep talking.
- Get the link into chat before anyone leaves. The board outlives the call only if somebody can find it.
When it goes wrong
DeafCaptions are off, or in the wrong language. Wrong language is the dangerous one — it answers confidently and wrongly. Set the language on the bot's own view; your caption button is irrelevant to what it hears.
Stuck in the lobbyMeet hides Admit behind the ⋮ menu on the "review potential risks" prompt. It looks deny-only. Also: a bot admitted after a long wait can come back deaf.
Board not visibleWriting the board and presenting it are two different things. If nobody is presenting, the room sees nothing — the agent should say so rather than describe a board that isn't up.
Talks too muchSwitch it to name-only mode mid-call. It keeps working and stops volunteering.
Held replies vanishWhen it yields mid-thought the reply is stashed and replayed at the next gap — or dropped if the room moved on. Both are normal.
Big roomsAbove roughly six people, voice stops working well: replies get composed, held and discarded. Use chat as the primary channel and let speech be opportunistic.
Know this before you bring it to someone else's meeting
Your reputation is in the room, not ours. Anyone present can talk to the agent and it may act on what they say — there is no authorized-speaker model. And the agent has whatever access your session has. Point it at a scratch directory for a call with people you don't know well.