Skip to main content
Always pass the global --json option when an agent reads the CLI output. A successful response contains schema_version, command, data and, for paginated commands, pagination. Read the result in data. Only follow pagination.next_offset if you need the next page. The CLI only reads the local database on your computer. It has no account, no sign-in and no remote source.

​
Check the installation

The report shows the CLI version, the selected database path, whether it opened read-only and the schema state. If ready is false, the command still prints the report and exits with code 1.

​
Find the meeting

Search is case-insensitive and covers the title and the ID. --folder includes subfolders. If several meetings match, ask the user to choose.

​
Read only what you need

Use meetings get when participants or action items matter. Use meetings note when the note content is enough.

​
Transcripts

Limits are counted in words. A page is 200 words by default, 500 at most. Stop paginating as soon as you have enough information.

​
Propose an edit

proposals create returns a pending proposal. Don’t claim that the meeting has changed. The user applies or declines it in the app; you can also decline it from the CLI. Only a pending proposal can be declined.

​
Import a recording

Only if the user explicitly asks for it, and with the app open:
The import creates a meeting and sends the audio to the transcription server configured in the app. Keep the returned job ID, and check processing_status and summary_status before announcing that it’s done. Details in the CLI reference.

​
Exports

Only export a full meeting if the user asks for a file:
The export refuses to replace an existing file. Only use --force after the user explicitly agrees to overwrite that exact path.
All options are in the CLI reference.