OpenClaw Meeting Bots Now Default to Durable Transcripts on Main

OpenClaw’s meeting integrations have crossed an important default boundary on main: Google Meet, Microsoft Teams and Zoom plugin surfaces are enabled by default, and a bot that joins a meeting automatically retains a durable speaker-attributed transcript and derived summary unless transcript persistence is disabled.

That is useful operationally and material for privacy, retention and compliance. Operators should make an explicit decision before adopting a release that contains this change.

The operator decision

• You want meeting notes: confirm the joining agent, storage location, retention process and access policy before relying on automatic capture.
• You do not want durable meeting records: set the existing transcript control to disabled and explicitly disable unused meeting plugins.
• You upgrade existing installations: do not assume “no plugin entry” means “off.” Teams and Zoom are designed to activate on existing installs with no explicit entries; an installed Google Meet plugin behaves the same way.
• You operate regulated or consent-sensitive meetings: treat this as recording-adjacent processing. Establish notice, consent, lawful basis and deletion procedures appropriate to your jurisdiction and organisation. This article is not legal advice.

The changes merged on 23 July. Confirm that your actual release includes PRs #112910, #113022, #113053 and #113122 before changing production policy.

Automatic capture replaces a manual second source

Before PR #113122, meeting bots could expose a bounded live caption tail, but operators had to start a separate transcript source to retain unified notes. A browser session or Gateway restart could otherwise take the useful meeting context with it.

The merged bridge subscribes to caption snapshots already owned by the shared meeting runtime. Google Meet, Teams and Zoom provide thin source adapters. The bridge writes speaker-attributed rows to OpenClaw’s transcript store and generates the existing derived summary when the meeting leaves.

Automatic persistence uses the existing transcripts.enabled control and defaults on. Setting it to false disables persistence, the transcript tool and automatic start. The explicit transcribe meeting mode remains a live-only bounded tail rather than silently becoming the durable store.

Stored meeting locators remove query strings, fragments and user information before persistence. Delivery retries are designed to be idempotent, and pending rows remain ordered across temporary storage failure while browser/audio teardown proceeds.

Interpretation: this is not just a convenience feature. The default lifecycle of spoken meeting content changes from potentially transient captions to an OpenClaw-owned durable record.

SQLite is now canonical; files are exports

PR #112910 moves meeting transcript sessions, utterances, summaries and export ownership into additive tables in the shared SQLite state database.

Commands such as openclaw transcripts path still expose familiar paths, but files at those paths are materialized exports rather than canonical runtime state. Backup and incident-recovery procedures must include the state database; copying only transcript export directories is no longer a complete preservation strategy.

Legacy JSON/JSONL transcript trees are migrated only through openclaw doctor --fix. The migration preflights and stages the whole tree, commits rows transactionally, records receipts, verifies content again and archives the source. Runtime does not dual-read old files or silently fall back to them.

Safe upgrade sequence:

1. back up the OpenClaw state directory and database using your normal consistent-snapshot procedure;
2. stop concurrent maintenance against the same state;
3. run the documented Doctor repair for the target release;
4. inspect migration receipts and recovery directories;
5. materialize a transcript export and compare speaker order and summary presence; and
6. restart, then confirm runtime reads the SQLite-backed record.

Do not delete legacy trees merely because an export command works. Preserve them until migration verification and your own backup checks are complete.

Plugin defaults change even without a meeting join

PR #113022 flips the bundled Teams and Zoom manifests to enabled by default. PR #113053 applies the same policy to the separately installed Google Meet plugin.

Default activation registers commands, tools and Gateway methods. Upstream’s isolated proof says it does not start a browser or join a meeting without a URL-bearing operation. Google Meet also remains uninstalled unless the external package has been installed.

That distinction prevents panic but does not remove the policy decision. A newly available agent tool can alter capability inventories and approval expectations even before anyone invokes it.

Operators who do not use these surfaces can disable them explicitly:

openclaw plugins disable teams-meetings
openclaw plugins disable zoom-meetings
openclaw plugins disable google-meet

Run only the commands relevant to plugins present in your installation, and verify effective status afterward rather than assuming configuration intent equals runtime state.

Retention questions to answer before rollout

At minimum, decide:

• which agents may join meetings;
• whether attendees are notified that captions become durable notes;
• who can use transcript search and export;
• how long SQLite-backed records and derived summaries are retained;
• whether backups inherit the same deletion policy;
• how sensitive meeting URLs and metadata are handled;
• what happens when capture is partial or summary generation fails; and
• whether disabling transcript persistence is enforced centrally or left to each operator.

The merged work records an owning agent and strips sensitive URL components, but those safeguards do not create an organisational retention policy for you.

Evidence and limits

Upstream reports focused transcript and meeting-adapter suites, live lineage for all three meeting platforms, and a packaged upgrade-survivor test from OpenClaw 2026.7.1 for the SQLite migration. Some tenant-specific Teams states and policy-dependent Zoom lobby/CAPTCHA paths were not live-exercised in the cited evidence.

OpenClaw Academy reviewed the official merged pull-request records and chronology. We did not join a real meeting, capture participant speech or independently execute the migration. Product behaviour and test results are therefore attributed to upstream evidence.

Bottom line

Automatic durable notes remove a clumsy manual step, but defaults carry governance consequences. A meeting bot that joins can now produce a lasting SQLite transcript and summary, while meeting plugin surfaces become available without the old enable step.

Before adopting the containing release, choose retention deliberately, disable what you do not use, back up the canonical database and test Doctor migration with non-sensitive records. “Default on” should never mean “nobody decided.”