teams-meetings plugin joins work links under
teams.microsoft.com/l/meetup-join/... and consumer links under
teams.live.com/meet/... as a guest in the OpenClaw Chrome profile. It does not
create meetings, dial in, call Microsoft Graph, or capture audio/video
recordings.
Use Meeting plugins for shared installation, modes,
Chrome and virtual-audio setup, transcripts, remote-node requirements, and
verification.
bidi mode supports the shared GPT-Live voice and native agent delegation.
Use the shared Live configuration
under plugins.entries.teams-meetings.config. Browser participant audio is
captured separately from native assistant-microphone injection, so Live can
hear interruptions while speaking.
Handle Teams policy and manual actions
The browser adapter dismisses the app interstitial, fills the guest name, turns the camera off, configures the microphone for the selected mode, and clicks the join button. It recognizes the consumer launcher and Chrome’sBlackHole 2ch (Virtual) labels. In-call state uses the hang-up control.
Tenant policy may require sign-in, email verification, organizer admission, or
a browser device-permission decision. The plugin reports these as
manualAction. Complete the requested step in the same OpenClaw Chrome profile,
then retry status or speech. It does not bypass tenant policy.
The consumer web client was live-validated in 2026.8.1 through the
interstitial, guest-name entry, microphone/camera toggles, lobby admission,
media permissions, in-call detection, live captions, BlackHole routing, leave,
and post-call detection. Work tenants can impose additional admission or leave-confirmation
policy.
Tool and Gateway surface
Theteams_meetings tool supports join, leave, status, transcript, and
speak. Gateway methods use teamsmeetings.*. The node command is
teamsmeetings.chrome.