Skip to main content
Use the global --json flag whenever an agent consumes CLI output. A successful response contains schema_version, command, data, and optional pagination. Read results from data. Follow pagination.next_offset only when you need another page. Meeting reads default to the local database. Use meetings --source cloud after anarlog auth login to read opted-in Cloud snapshots, or meetings --source auto to use Cloud only when the local database is absent.

​
Resolve meeting context

Search is case-insensitive across meeting titles and IDs. If several meetings match, ask the user to choose one.

​
Read the smallest useful surface

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

​
Stage an edit

The create command returns a pending proposal. Do not claim the meeting changed. Open the meeting in the desktop app to apply it, or decline it from the CLI or desktop app. Only pending proposals can be declined.

​
Transcripts

Transcript limits are measured in words. A page defaults to 200 words and caps at 500. Stop paging once you have enough evidence.

​
Diagnose setup

The report includes the CLI version, resolved database path, read-only connection status, and schema readiness. When ready is false, the command still prints the report to standard output and exits with status 1.

​
Exports

Only export a complete meeting when the user explicitly requests a file:
Export refuses to replace an existing file. Use --force only after the user explicitly approves overwriting that exact path.
See the CLI reference for every option.