@@ -112,6 +112,8 @@ openclaw googlemeet join https://meet.google.com/new-abcd-xyz --transport chrome
112112 pinned Chrome node, opens `https://meet.google.com/new`, waits for Google to
113113 redirect to a real meeting-code URL, then returns that URL. This path requires
114114 the OpenClaw Chrome profile on the node to already be signed in to Google.
115+ Browser automation handles Meet's own first-run microphone prompt; that prompt
116+ is not treated as a Google login failure.
115117116118The command output includes a `source` field (`api` or `browser`) so agents can
117119explain which path was used.
@@ -271,11 +273,17 @@ phrase, and prints session health:
271273openclaw googlemeet test-speech https://meet.google.com/abc-defg-hij
272274```
273275274-If the browser profile is not signed in, Meet is waiting for host admission, or
275-Chrome needs microphone/camera permission, the join/test-speech result reports
276+During join, OpenClaw browser automation fills the guest name, clicks Join/Ask
277+to join, and accepts Meet's first-run "Use microphone" choice when that prompt
278+appears. During browser-only meeting creation, it can also continue past the
279+same prompt without microphone if Meet does not expose the use-microphone button.
280+If the browser profile is not signed in, Meet is waiting for host
281+admission, Chrome needs microphone/camera permission, or Meet is stuck on a
282+prompt automation could not resolve, the join/test-speech result reports
276283`manualActionRequired: true` with `manualActionReason` and
277-`manualActionMessage`. Agents should stop retrying the join, report that message
278-to the operator, and retry only after the manual browser action is complete.
284+`manualActionMessage`. Agents should stop retrying the join, report that exact
285+message plus the current `browserUrl`/`browserTitle`, and retry only after the
286+manual browser action is complete.
279287280288If `chromeNode.node` is omitted, OpenClaw auto-selects only when exactly one
281289connected node advertises both `googlemeet.chrome` and browser control. If
@@ -784,9 +792,17 @@ Common manual actions:
784792785793- Sign in to the Chrome profile.
786794- Admit the guest from the Meet host account.
787-- Grant Chrome microphone/camera permissions.
795+- Grant Chrome microphone/camera permissions when Chrome's native permission
796+ prompt appears.
788797- Close or repair a stuck Meet permission dialog.
789798799+Do not report "not signed in" just because Meet shows "Do you want people to
800+hear you in the meeting?" That is Meet's audio-choice interstitial; OpenClaw
801+clicks **Use microphone** through browser automation when available and keeps
802+waiting for the real meeting state. For create-only browser fallback, OpenClaw
803+may click **Continue without microphone** because creating the URL does not need
804+the realtime audio path.
805+790806### Meeting creation fails
791807792808`googlemeet create` first uses the Google Meet API `spaces.create` endpoint
@@ -803,6 +819,11 @@ to the pinned Chrome node browser. Confirm:
803819`googlemeet.chrome`.
804820- For browser fallback: the OpenClaw Chrome profile on that node is signed in
805821 to Google and can open `https://meet.google.com/new`.
822+- For browser fallback: if Meet shows "Do you want people to hear you in the
823+ meeting?", leave the tab open. OpenClaw should click **Use microphone** or, for
824+ create-only fallback, **Continue without microphone** through browser
825+ automation and continue waiting for the generated Meet URL. If it cannot, the
826+ error should mention `meet-audio-choice-required`, not `google-login-required`.
806827807828### Agent joins but does not talk
808829此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。