11---
2-summary: "CLI reference for `openclaw meeting-notes` (list, show, and locate stored meeting notes)"
2+summary: "CLI reference for `openclaw transcripts` (list, show, and locate stored transcripts)"
33read_when:
4- - You want to read stored meeting note summaries from the terminal
5- - You need the path to a meeting notes markdown summary
6- - You are debugging the meeting-notes plugin storage layout
7-title: "Meeting Notes CLI"
4+ - You want to read stored transcript summaries from the terminal
5+ - You need the path to a transcripts markdown summary
6+ - You are debugging the core transcripts storage layout
7+title: "Transcripts CLI"
88---
9910-# `openclaw meeting-notes`
10+# `openclaw transcripts`
111112-Inspect meeting notes written by the external `meeting-notes` plugin. This CLI
13-is read-only and is available when that plugin is installed or loaded from
14-source. Capture, import, and summarization are owned by the `meeting_notes`
15-agent tool and by configured auto-start sources.
12+Inspect transcripts written by OpenClaw's core `transcripts` tool. This CLI is
13+read-only; capture, import, and summarization are owned by the agent tool and
14+configured auto-start sources.
16151716Use the CLI when you want to find yesterday's notes, open the Markdown file in
1817an editor, feed a transcript to another tool, or debug where a session landed on
@@ -21,7 +20,7 @@ disk. It does not start or stop capture.
2120Artifacts live under the OpenClaw state directory:
22212322```text
24-$OPENCLAW_STATE_DIR/meeting-notes/YYYY-MM-DD/<session>/
23+$OPENCLAW_STATE_DIR/transcripts/YYYY-MM-DD/<session>/
2524 metadata.json
2625 transcript.jsonl
2726 summary.json
@@ -35,17 +34,17 @@ session directory is a safe filesystem segment derived from the session id.
3534## Commands
36353736```bash
38-openclaw meeting-notes list
39-openclaw meeting-notes show <session>
40-openclaw meeting-notes show YYYY-MM-DD/<session>
41-openclaw meeting-notes path <session>
42-openclaw meeting-notes path YYYY-MM-DD/<session>
43-openclaw meeting-notes path <session> --dir
44-openclaw meeting-notes path <session> --metadata
45-openclaw meeting-notes path <session> --transcript
46-openclaw meeting-notes list --json
47-openclaw meeting-notes show <session> --json
48-openclaw meeting-notes path <session> --json
37+openclaw transcripts list
38+openclaw transcripts show <session>
39+openclaw transcripts show YYYY-MM-DD/<session>
40+openclaw transcripts path <session>
41+openclaw transcripts path YYYY-MM-DD/<session>
42+openclaw transcripts path <session> --dir
43+openclaw transcripts path <session> --metadata
44+openclaw transcripts path <session> --transcript
45+openclaw transcripts list --json
46+openclaw transcripts show <session> --json
47+openclaw transcripts path <session> --json
4948```
50495150- `list`: list stored sessions, date-qualified selector, start time, title, and `summary.md` path.
@@ -57,7 +56,7 @@ openclaw meeting-notes path <session> --json
5756- `--json`: print machine-readable output.
58575958When a human session id repeats across days, use the date-qualified selector
60-from `list`, for example `openclaw meeting-notes show 2026-05-22/standup`.
59+from `list`, for example `openclaw transcripts show 2026-05-22/standup`.
6160Default session ids include a timestamp and random suffix; configure fixed
6261session ids only when they are unique within the day.
6362@@ -66,7 +65,7 @@ session ids only when they are unique within the day.
6665`list` prints one session per line:
67666867```text
69-2026-05-22/standup 2026-05-22T09:00:00.000Z Weekly standup /Users/alex/.openclaw/meeting-notes/2026-05-22/standup/summary.md
68+2026-05-22/standup 2026-05-22T09:00:00.000Z Weekly standup /Users/alex/.openclaw/transcripts/2026-05-22/standup/summary.md
7069```
71707271The output is tab-separated. The columns are selector, start time, title, and
@@ -91,13 +90,13 @@ and whether that file exists.
91909291## Many meetings per day
939294-Meeting Notes groups sessions by date, then by session id. Ten meetings on one
93+Transcripts groups sessions by date, then by session id. Ten meetings on one
9594day become ten sibling folders:
96959796```text
98-~/.openclaw/meeting-notes/2026-05-22/
99- meeting-2026-05-22T09-00-00-000Z-a1b2c3d4/
100- meeting-2026-05-22T10-30-00-000Z-b2c3d4e5/
97+~/.openclaw/transcripts/2026-05-22/
98+ transcript-2026-05-22T09-00-00-000Z-a1b2c3d4/
99+ transcript-2026-05-22T10-30-00-000Z-b2c3d4e5/
101100 standup/
102101```
103102@@ -112,7 +111,41 @@ write `summary.md` immediately after import. A session can still appear in
112111or metadata was written before any utterances arrived.
113112114113Use `path <session> --transcript` to inspect the append-only transcript, and use
115-the `meeting_notes` tool action `summarize` to regenerate the Markdown summary.
114+the `transcripts` tool action `summarize` to regenerate the Markdown summary.
116115117-See [Meeting Notes](/plugins/meeting-notes) for configuration, auto-start, and
118-source-provider details.
116+## Configuration
117+118+Transcript capture is opt-in because live sources can join and record meeting
119+audio. Enable the tool with top-level `transcripts.enabled`:
120+121+```json
122+{
123+"transcripts": {
124+"enabled": true,
125+"maxUtterances": 2000
126+ }
127+}
128+```
129+130+Configure auto-start sources with `transcripts.autoStart` in `openclaw.json`.
131+Each entry is enabled by being present; omit an entry to disable that source.
132+133+```json
134+{
135+"transcripts": {
136+"enabled": true,
137+"autoStart": [
138+ {
139+"providerId": "discord-voice",
140+"guildId": "1234567890",
141+"channelId": "2345678901"
142+ },
143+ {
144+"providerId": "slack-huddle",
145+"accountId": "workspace",
146+"channelId": "C123"
147+ }
148+ ]
149+ }
150+}
151+```
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。