chore(sync): mirror docs from openclaw/openclaw@52cc1ebac7

This commit is contained in:
openclaw-docs-sync[bot] 2026-04-25 01:20:46 +00:00
parent 7cc5fca809
commit 6f7efd7323
2 changed files with 40 additions and 2 deletions

View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "0bd8d0bba08b386ca975510235e00df2139b3e70",
"syncedAt": "2026-04-25T01:15:06.736Z"
"sha": "52cc1ebac792c5063e5fbf0e4ffa39036a84072c",
"syncedAt": "2026-04-25T01:19:22.735Z"
}

View File

@ -728,11 +728,29 @@ openclaw googlemeet test-speech https://meet.google.com/abc-defg-hij \
Expected Chrome-node state:
- `googlemeet setup` is all green.
- `googlemeet setup` includes `chrome-node-connected` when Chrome-node is the
default transport or a node is pinned.
- `nodes status` shows the selected node connected.
- The selected node advertises both `googlemeet.chrome` and `browser.proxy`.
- The Meet tab joins the call and `test-speech` returns Chrome health with
`inCall: true`.
For a remote Chrome host such as a Parallels macOS VM, this is the shortest
safe check after updating the Gateway or the VM:
```bash
openclaw googlemeet setup
openclaw nodes status --connected
openclaw nodes invoke \
--node parallels-macos \
--command googlemeet.chrome \
--params '{"action":"setup"}'
```
That proves the Gateway plugin is loaded, the VM node is connected with the
current token, and the Meet audio bridge is available before an agent opens a
real meeting tab.
For a Twilio smoke, use a meeting that exposes phone dial-in details:
```bash
@ -798,6 +816,26 @@ The Gateway config must allow those node commands:
}
```
If `googlemeet setup` fails `chrome-node-connected` or the Gateway log reports
`gateway token mismatch`, reinstall or restart the node with the current Gateway
token. For a LAN Gateway this usually means:
```bash
OPENCLAW_ALLOW_INSECURE_PRIVATE_WS=1 \
openclaw node install \
--host <gateway-lan-ip> \
--port 18789 \
--display-name parallels-macos \
--force
```
Then reload the node service and re-run:
```bash
openclaw googlemeet setup
openclaw nodes status --connected
```
### Browser opens but agent cannot join
Run `googlemeet test-speech` and inspect the returned Chrome health. If it