



























@@ -169,7 +169,7 @@ Set config under `plugins.entries.google-meet.config`:
169169 realtime: {
170170 provider: "openai",
171171 model: "gpt-realtime",
172- instructions: "You are joining a private Google Meet as Peter's OpenClaw agent. Keep replies brief unless asked.",
172+ instructions: "You are joining a private Google Meet as my OpenClaw agent. Keep replies brief unless asked.",
173173 toolPolicy: "safe-read-only",
174174 providers: {
175175 openai: {
@@ -207,19 +207,36 @@ Agents can use the `google_meet` tool:
207207Use `action: "status"` to list active sessions or inspect a session ID. Use
208208`action: "leave"` to mark a session ended.
209209210+## Realtime agent consult
211+212+Chrome realtime mode is optimized for a live voice loop. The realtime voice
213+provider hears the meeting audio and speaks through the configured audio bridge.
214+When the realtime model needs deeper reasoning, current information, or normal
215+OpenClaw tools, it can call `openclaw_agent_consult`.
216+217+The consult tool runs the regular OpenClaw agent behind the scenes with recent
218+meeting transcript context and returns a concise spoken answer to the realtime
219+voice session. The voice model can then speak that answer back into the meeting.
220+221+`realtime.toolPolicy` controls the consult run:
222+223+- `safe-read-only`: expose the consult tool and limit the regular agent to
224+`read`, `web_search`, `web_fetch`, `x_search`, `memory_search`, and
225+`memory_get`.
226+- `owner`: expose the consult tool and let the regular agent use the normal
227+ agent tool policy.
228+- `none`: do not expose the consult tool to the realtime voice model.
229+230+The consult session key is scoped per Meet session, so follow-up consult calls
231+can reuse prior consult context during the same meeting.
232+210233## Notes
211234212235Google Meet's official media API is receive-oriented, so speaking into a Meet
213236call still needs a participant path. This plugin keeps that boundary visible:
214237Chrome handles browser participation and local audio routing; Twilio handles
215238phone dial-in participation.
216239217-Realtime mode gives the voice model one tool, `openclaw_agent_consult`, unless
218-`realtime.toolPolicy` is `none`. The tool asks the normal OpenClaw agent for a
219-concise spoken answer, using recent meeting transcript as context. With
220-`safe-read-only`, the consult run is limited to read/search/memory tools. With
221-`owner`, it inherits the normal agent tool policy.
222-223240Chrome realtime mode needs either:
224241225242- `chrome.audioInputCommand` plus `chrome.audioOutputCommand`: OpenClaw owns the
@@ -231,3 +248,7 @@ Chrome realtime mode needs either:
231248For clean duplex audio, route Meet output and Meet microphone through separate
232249virtual devices or a Loopback-style virtual device graph. A single shared
233250BlackHole device can echo other participants back into the call.
251+252+`googlemeet leave` stops the command-pair realtime audio bridge for Chrome
253+sessions. For Twilio sessions delegated through the Voice Call plugin, it also
254+hangs up the underlying voice call.
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。