From fa8183729d690e3cd1e1de86eedc851441df4c98 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Sat, 25 Apr 2026 19:05:31 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@5eab16e0863f30616e3a7999fb9268330e7a75e3 --- .openclaw-sync/source.json | 4 ++-- docs/plugins/google-meet.md | 8 ++++++++ 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index b95611989..ec3c7a22b 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "8170df912792d9894f0bf1b7d1dc507758afc18b", - "syncedAt": "2026-04-25T19:00:52.592Z" + "sha": "5eab16e0863f30616e3a7999fb9268330e7a75e3", + "syncedAt": "2026-04-25T19:03:57.345Z" } diff --git a/docs/plugins/google-meet.md b/docs/plugins/google-meet.md index 0cf41222c..00707f980 100644 --- a/docs/plugins/google-meet.md +++ b/docs/plugins/google-meet.md @@ -79,6 +79,8 @@ audio bridge, node pinning, delayed realtime intro, and, when Twilio delegation is configured, whether the `voice-call` plugin and Twilio credentials are ready. Treat any `ok: false` check as a blocker before asking an agent to join. Use `openclaw googlemeet setup --json` for scripts or machine-readable output. +Use `--transport chrome`, `--transport chrome-node`, or `--transport twilio` +to preflight a specific transport before an agent tries it. Join a meeting: @@ -303,11 +305,17 @@ display name, or remote IP. Common failure checks: +- `Configured Google Meet node ... is not usable: offline`: the pinned node is + known to the Gateway but unavailable. Agents should treat that node as + diagnostic state, not as a usable Chrome host, and report the setup blocker + instead of falling back to another transport unless the user asked for that. - `No connected Google Meet-capable node`: start `openclaw node run` in the VM, approve pairing, and make sure `openclaw plugins enable google-meet` and `openclaw plugins enable browser` were run in the VM. Also confirm the Gateway host allows both node commands with `gateway.nodes.allowCommands: ["googlemeet.chrome", "browser.proxy"]`. +- `BlackHole 2ch audio device not found`: install `blackhole-2ch` on the host + being checked and reboot before using local Chrome audio. - `BlackHole 2ch audio device not found on the node`: install `blackhole-2ch` in the VM and reboot the VM. - Chrome opens but cannot join: sign in to the browser profile inside the VM, or