Get started

Meeting Notes CLI

Edit source

openclaw meeting-notes

Inspect meeting notes written by the external meeting-notes plugin. This CLI is read-only and is available when that plugin is installed or loaded from source. Capture, import, and summarization are owned by the meeting_notes agent tool and by configured auto-start sources.

Use the CLI when you want to find yesterday's notes, open the Markdown file in an editor, feed a transcript to another tool, or debug where a session landed on disk. It does not start or stop capture.

Artifacts live under the OpenClaw state directory:

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

The default state directory is ~/.openclaw; set OPENCLAW_STATE_DIR to use a different one. The date directory comes from the session start time, and the session directory is a safe filesystem segment derived from the session id.

Commands

bash
openclaw meeting-notes listopenclaw meeting-notes show <session>openclaw meeting-notes show YYYY-MM-DD/<session>openclaw meeting-notes path <session>openclaw meeting-notes path YYYY-MM-DD/<session>openclaw meeting-notes path <session> --diropenclaw meeting-notes path <session> --metadataopenclaw meeting-notes path <session> --transcriptopenclaw meeting-notes list --jsonopenclaw meeting-notes show <session> --jsonopenclaw meeting-notes path <session> --json
  • list: list stored sessions, date-qualified selector, start time, title, and summary.md path.
  • show <session>: print the stored summary.md.
  • path <session>: print the summary.md path.
  • path <session> --dir: print the session directory.
  • path <session> --metadata: print metadata.json.
  • path <session> --transcript: print transcript.jsonl.
  • --json: print machine-readable output.

When a human session id repeats across days, use the date-qualified selector from list, for example openclaw meeting-notes show 2026-05-22/standup. Default session ids include a timestamp and random suffix; configure fixed session ids only when they are unique within the day.

Output

list prints one session per line:

text
2026-05-22/standup  2026-05-22T09:00:00.000Z  Weekly standup  /Users/alex/.openclaw/meeting-notes/2026-05-22/standup/summary.md

The output is tab-separated. The columns are selector, start time, title, and summary path. The selector is the safest value to pass back to show or path.

list --json prints objects with:

  • sessionId
  • selector
  • date
  • title
  • startedAt
  • stoppedAt
  • source
  • path
  • summaryPath
  • hasSummary

show --json returns the stored session metadata, selector, session directory, summary path, and summary Markdown text. path --json returns the selected path and whether that file exists.

Many meetings per day

Meeting Notes groups sessions by date, then by session id. Ten meetings on one day become ten sibling folders:

text
~/.openclaw/meeting-notes/2026-05-22/  meeting-2026-05-22T09-00-00-000Z-a1b2c3d4/  meeting-2026-05-22T10-30-00-000Z-b2c3d4e5/  standup/

Use default generated ids for most automation. Use a fixed id such as standup only when the same id will not be used twice on the same date.

Missing summaries

Live sessions write summary.md when the session stops. Imported transcripts write summary.md immediately after import. A session can still appear in list without a summary when capture is active, a provider failed during stop, or metadata was written before any utterances arrived.

Use path <session> --transcript to inspect the append-only transcript, and use the meeting_notes tool action summarize to regenerate the Markdown summary.

See Meeting Notes for configuration, auto-start, and source-provider details.

Was this useful?