vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 08:00:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(google-meet): guard linux chrome realtime tool actions

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-02 08:07:05 +01:00
parent 74a55d7b21
commit afd0a7b403
6 changed files with 109 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
docs/plugins/google-meet.md
View File

@@ -119,6 +119,13 @@ Or let an agent join through the `google_meet` tool:
}
```
The agent-facing `google_meet` tool stays available on non-macOS hosts for
artifact, calendar, setup, transcribe, Twilio, and `chrome-node` flows. Local
Chrome realtime actions are blocked there because the bundled realtime Chrome
audio path currently depends on macOS `BlackHole 2ch`. On Linux, use
`mode: "transcribe"`, Twilio dial-in, or a macOS `chrome-node` host for realtime
Chrome participation.
Create a new meeting and join it:
```bash
@@ -1267,6 +1274,12 @@ If you just edited `plugins.entries.google-meet`, restart or reload the Gateway.
The running agent only sees plugin tools registered by the current Gateway
process.
On non-macOS Gateway hosts, the agent-facing `google_meet` tool stays visible,
but local Chrome realtime actions are blocked before they hit the audio bridge.
Local Chrome realtime audio currently depends on macOS `BlackHole 2ch`, so
Linux agents should use `mode: "transcribe"`, Twilio dial-in, or a macOS
`chrome-node` host instead of the default local Chrome realtime path.
### No connected Google Meet-capable node
On the node host, run: