openclaw/docs/plugins/meeting-notes.md

summary, read_when, title

summary	read_when	title
Meeting Notes plugin: capture transcripts from Discord voice and imported meeting sources, then write summaries	You want OpenClaw to take meeting notes You are wiring Discord voice, Google Meet, Slack huddles, or another meeting source into notes You need the meeting_notes tool contract	Meeting Notes plugin

The Meeting Notes plugin is the generic notes layer for live calls and imported meeting transcripts. It owns transcript storage, summary rendering, and the meeting_notes tool. Channel plugins own capture.

Source model

Meeting sources register meetingNotesSourceProviders through the plugin SDK. The first live provider is discord-voice; the built-in manual-transcript provider imports post-meeting transcripts.

• live-audio: source joins or listens to a call and streams final utterances.
• live-caption: source reads captions from a browser or meeting surface.
• posthoc-transcript: source imports a transcript or notes artifact after the meeting.
• recording-stt: source transcribes a recording before importing utterances.

This keeps Discord, Google Meet, Slack huddles, and future meeting surfaces out of the notes engine. Each source supplies speaker-labeled utterances; Meeting Notes writes the artifacts and summary.

Enable

Meeting Notes is an external source plugin in this repository. It is not part of the core OpenClaw npm package and becomes available only when the plugin is installed or loaded from source. Once loaded, it is enabled by default unless plugins.enabled is false, plugins.deny includes meeting-notes, or plugins.entries.meeting-notes.enabled is false.

Use autoStart when OpenClaw should begin notes capture automatically on gateway startup:

{
  plugins: {
    entries: {
      "meeting-notes": {
        config: {
          autoStart: [
            {
              providerId: "discord-voice",
              guildId: "123",
              channelId: "456",
              title: "Weekly planning",
            },
          ],
        },
      },
    },
  },
}

Discord voice capture still needs normal Discord voice setup and permissions. See Discord voice.

Transcription uses the normal audio understanding stack configured under tools.media.audio. If no explicit audio model is configured, OpenClaw tries configured provider keys first, then local audio engines such as sherpa-onnx, whisper-cli, or whisper when available.

Tool

Use meeting_notes with an action:

• status: list registered providers and active sessions.
• start: start a live notes session.
• stop: stop a live session and write summary.md.
• import: import a transcript and write summary.md.
• summarize: regenerate a summary for an existing session.

Discord live notes require providerId: "discord-voice", plus guildId and channelId. accountId is optional when only one Discord account is active.

{
  "action": "start",
  "providerId": "discord-voice",
  "guildId": "123",
  "channelId": "456",
  "title": "Weekly planning"
}

Stop by session id:

{
  "action": "stop",
  "sessionId": "meeting-2026-05-22T10-00-00-000Z-a1b2c3d4"
}

Import a transcript:

{
  "action": "import",
  "providerId": "manual-transcript",
  "title": "Design review",
  "transcript": "Alex: We decided to ship the Discord source first.\nSam: Action item: add Slack huddle import later."
}

Artifacts are stored under the OpenClaw state directory:

• meeting-notes/YYYY-MM-DD/<session>/metadata.json
• meeting-notes/YYYY-MM-DD/<session>/transcript.jsonl
• meeting-notes/YYYY-MM-DD/<session>/summary.json
• meeting-notes/YYYY-MM-DD/<session>/summary.md

The date directory comes from the session start time, so multiple meetings per day stay grouped. If a human session id repeats across days, use the date-qualified selector from openclaw meeting-notes list, such as 2026-05-22/standup.

By default, OpenClaw generates timestamped session ids, so many meetings on the same day get separate directories. Configure sessionId only when that id is unique for the day.

Use the read-only CLI to find or print stored summaries:

openclaw meeting-notes list
openclaw meeting-notes show <session>
openclaw meeting-notes path <session>

See Meeting Notes CLI for the full command reference.

For long meetings, utterances are appended to transcript.jsonl as they arrive. Summary generation reads a bounded window controlled by plugins.entries.meeting-notes.config.maxUtterances (default: 2000) so a multi-hour call does not require unbounded summary memory.

Slack Huddles

Slack huddles should use a post-meeting source first. Slack does not expose a general bot-join live huddle audio API, but Slack huddle notes and transcript artifacts can be imported later by a Slack-owned provider.