Meet Local Recorder

Local recordings. Useful meeting notes. Optional caption-based AI answers.

Version 0.4.2 · Updated 15 October 2026

Record your next meeting

  1. Install the extension, then open Setup & recordings. Allow your microphone and choose the same device as Meet, or disable microphone inclusion.
  2. Refresh Meet after installation, join the call and tell participants you are recording.
  3. Open the recorder from Chrome's toolbar and choose Start recording. Pause, resume and mark moments from the toolbar or archive.
  4. Choose Stop & save or leave Meet. Keep Chrome running until finalization completes. WebM files save under Chrome downloads / Meet Recordings by default, with a local backup in the archive.

Windows & Linux setup

Use desktop Chrome 116 or newer. Allow microphone access in Chrome and your operating system, then select the same microphone as Meet. If a device is disconnected, reconnect it and select it again in setup. Meeting audio comes from the Meet tab; independent system sounds are not captured.

Pause omits that time from the saved file while the meeting stays audible. Use Resume to continue or Stop & save while paused. Cancel start is available if device setup is delayed. Media requests time out after 30 seconds. A control error is kept with the local backup so you can inspect and retry the download.

Optional meeting assistant

In versions with the assistant, open Meeting assistant, save your own OpenRouter key and allow the optional OpenRouter connection. Start recording, enable the assistant for that recording, and turn on Meet captions in the spoken language. Type a question or opt into automatic detection. Answer length and tone are configurable; English is requested regardless of input language. Free models only, no paid fallback. Free-provider quotas and speed vary.

Meet controls are hidden by default. Answers live in a separate extension window. Share only the intended tab/app, keep the assistant outside it and use Hide answers before sharing. Full-screen capture can include visible assistant content.

Recovery and limitations

If a download fails, open the archive and retry Download again. A partial/interrupted backup may be incomplete. Stop and save before sleep, browser restart or an extension update. Do not uninstall to update, because that removes local backups.

Meet layout changes, localized controls, physical microphone devices, long sessions and free-model availability can affect behavior. Captions must be enabled and recognized. Manual questions work when captions are unavailable. This does not provide independent speech transcription, perfect question detection, guaranteed instant answers, or invisibility to operating-system capture.

0.4.2 release notes: cancellable startup, responsive Stop during control changes, keyboard status updates, preserved control errors, correct paused-time metadata and Windows-safe download folders. Store updates become available after Google approval.

Privacy & data handling

Local recording

Google Meet tab video and audio, plus the selected microphone while Meet reports it unmuted, are recorded in this extension's local browser archive and downloaded to your computer. Recording media is not uploaded to an AI provider. Backups and notebook entries remain until you delete them or remove the extension.

Optional meeting assistant

The assistant is off by default and must be enabled for each recording. It reads text from recognized Meet caption regions. Recent caption text and questions (which may include personal information or private communications) are sent over HTTPS directly to OpenRouter and its selected model provider to generate answers. If automatic detection is enabled, detected questions trigger requests without a click for each one. No meeting chat or broad page-body scraping is intended. Manual questions work when captions are unavailable.

Do not enable this feature for content you do not want to share with those providers. Inform meeting participants when appropriate. The extension has no developer-operated AI backend. Provider handling and retention are governed by OpenRouter's privacy policy and the selected model provider's policies. Free-model routing can select different providers; it is not a promise of confidential or zero-retention inference.

Keys, settings and temporary text

Your OpenRouter key is kept in trusted extension session storage, cleared with the browser session. It is used only in the request's authorization header to OpenRouter. This extension does not remember it in local/sync storage or include it in Meet pages, recordings, answers or diagnostic errors. Preferences and request-budget counters are local. Temporary caption context, questions, answers and cache are not saved in the recording archive or analytics logs. Pausing/stopping/settings changes disable the assistant and cancel pending work. Cancellation cannot retract a request already received by a provider.

Sharing and screenshots

Answers appear in a separate extension window, never over the Meet page. Meet controls are hidden by default. A curtain covers answers manually and when recognized Meet state reports presentation. Detection can miss UI changes or localized controls. The curtain does not cover settings/key-entry fields or copies elsewhere. No extension can guarantee hiding visible windows from operating-system screenshots, full-screen recordings or entire-screen sharing. Share only the intended tab/app and keep the assistant window outside it.

Permissions and deletion

Required Meet host access identifies controls and recognized captions. Optional OpenRouter host permission is requested from assistant setup. Tab capture, offscreen media, storage and downloads support local recording. Unlimited storage relaxes browser quota, not physical disk limits. Delete local backups in the archive, remove the API key in assistant settings, or remove the extension to delete extension-held data. Removing the extension does not delete files already downloaded or data already sent to providers.

Support

Use the Chrome Web Store listing support link or publisher contact. Never include API keys or private meeting text in public support posts.