Call language
The bot reads Meet's captions, not audio. Set the caption language wrong and it doesn't go quiet — it becomes confidently wrong.
Your agent doesn't transcribe audio. It reads Google Meet's live captions, which means
Meet's caption language decides what the agent hears.
google-meet-provider.js:2995
Set it wrong and the failure is quiet: Meet turns perfectly good speech into phonetic
gibberish, and the agent answers the gibberish. It doesn't go silent — it becomes confidently
wrong, and nobody notices until someone reads the transcript.
Set it before you talk
Caption language is per participant in Meet — there is no host-level control, so the
setting that matters is the one on the bot's own view, not yours. An agent can set it
directly; the tool walks Meet's own settings dialog.
server.js:2308
Use a BCP-47 tag: en-US, de-DE, fr-FR, es-ES, pt-BR, ja-JP.
If it seems deaf
| Symptom | What it usually is |
|---|---|
| Answers nothing at all | Captions are off. No captions, no hearing. |
| Answers the wrong question, fluently | Caption language mismatch — it heard different words |
| Went deaf after being admitted late | It sat in the lobby too long and burned its caption retries |
| Missed a stretch, then recovered | The caption pane scrolled past the turn it was holding |
The last two are known app bugs, not you doing something wrong.
vibeconf-app#497 · #389