What the bot hears
You're about to admit a software teammate into a real meeting. Here is exactly what it can hear and see, where that goes, and how to turn any of it off. If the app's behavior ever differs from this page, that's a bug — tell us.
👂 What it hears and sees
The bot listens by reading Google Meet's live captions — the same transcript every participant can already see on screen. No captions, no hearing. It sees what any participant sees: tiles, names, screen shares, and the Meet chat. It joins with a visible name and face, knocks, and enters only when a host clicks Admit. It cannot lurk.
🏠 Where your data lives
The bot's brain is your Claude Code, running on your computer, on your Anthropic subscription. Meeting transcripts flow into your local session — the same place your coding sessions live. We never hold your API keys or your Claude account, and there is no Vibeconferencing account to create.
During the beta, the app ships its session log to our backend so we can debug problems on machines we can't see — and that log can include transcript text. This is on by default while the userbase is friends-and-family, because those logs are how bugs get fixed the same night.
Turn it off any time: tell your agent "set remoteLogging to false" — it takes effect immediately, no restart. Off means logs stay on your machine, full stop.
A call receipt (the summary page) is created and published only when you or your agent runs the receipt flow — nothing auto-publishes. Read it before you share it; it's a web page.
🚪 How you get rid of it
Say so — "we're done, you can go" and it leaves. Kick it — it's an ordinary Meet participant, so any host can remove it exactly like a person. Quit the app — the bot's body is a program on your Mac; quitting it ends the bot. Hang up — when the meeting ends, it wraps up and shuts itself down, with a five-minute backstop so it can't sit there forever writing.
It also can't hide: it joins with a visible name and face, in the participant list, like everyone else. There is no invisible mode and we won't build one.
The bot does not yet auto-leave when it's the last one in an empty room. If everyone drops and nobody dismisses it, it can linger until you quit the app. It costs you nothing when it does — the bot runs on your own machine, not a meter — but it's still wrong, and it's on the list.
🤝 Meeting etiquette (the human part)
- Tell the room. The bot announces itself by name, but say it out loud too: "I'm bringing my agent in — it reads the captions." The Admit click is the consent moment; treat it that way.
- Transcripts are notes. Legally and socially, treat what the bot retains like notes a colleague is taking. If a topic shouldn't be in anyone's notes, ask the bot to leave — "we're done, you can go" works.
- Recording laws vary by place. Captions-reading isn't audio recording, but when in doubt, get the same permission you'd get to record.
🔓 Check our work
Every claim on this page is checkable: read the code. Found a gap between this page and the code? That's the most valuable bug report we can get — jimmy@vibeconf.app.
better call jimmy · field guide · docs