Summary
A fresh AlphaClaw Docker deployment can install and use Gog, but Google Meet is not available through OpenClaw unless the operator separately installs and enables @openclaw/google-meet.
That distinction is easy to miss: Gog's Meet CLI and OpenClaw's Google Meet participant plugin are separate integrations with separate OAuth configuration.
Reproduction
- Start a current AlphaClaw Docker deployment.
- Complete the Google/Gog authorization flow.
- Try to use the OpenClaw Meet integration.
Before a manual plugin install, the Google Meet command is unavailable because the plugin package is not present/registered.
Installing and enabling the matching official plugin resolves command discovery:
openclaw plugins install @openclaw/google-meet
openclaw plugins enable google-meet
# restart gateway
The plugin then correctly reports that it needs its own OAuth configuration. This is expected behavior, but it is not surfaced by the AlphaClaw onboarding.
Expected behavior
Either:
- include the version-compatible
@openclaw/google-meet plugin in the AlphaClaw image and make it opt-in during setup, or
- have onboarding explicitly detect that the plugin is absent and offer the install/enable path.
Please also document that Gog OAuth/keyring state is distinct from the Google Meet plugin's OAuth configuration, rather than implying that authorizing Google once enables both.
Why this matters
Without that guidance, an operator can have a healthy Google authorization and enabled Google APIs while Meet still appears broken, because the required plugin was never installed.
Summary
A fresh AlphaClaw Docker deployment can install and use Gog, but Google Meet is not available through OpenClaw unless the operator separately installs and enables
@openclaw/google-meet.That distinction is easy to miss: Gog's Meet CLI and OpenClaw's Google Meet participant plugin are separate integrations with separate OAuth configuration.
Reproduction
Before a manual plugin install, the Google Meet command is unavailable because the plugin package is not present/registered.
Installing and enabling the matching official plugin resolves command discovery:
The plugin then correctly reports that it needs its own OAuth configuration. This is expected behavior, but it is not surfaced by the AlphaClaw onboarding.
Expected behavior
Either:
@openclaw/google-meetplugin in the AlphaClaw image and make it opt-in during setup, orPlease also document that Gog OAuth/keyring state is distinct from the Google Meet plugin's OAuth configuration, rather than implying that authorizing Google once enables both.
Why this matters
Without that guidance, an operator can have a healthy Google authorization and enabled Google APIs while Meet still appears broken, because the required plugin was never installed.