CLI for agents

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.

Resolve meeting context

mico --json meetings list --query "weekly planning" --limit 10
mico --json meetings get MEETING_ID

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

Read the smallest useful surface

mico --json meetings note MEETING_ID --kind note
mico --json meetings note MEETING_ID --kind summary
mico --json meetings history MEETING_ID --limit 10 --offset 0

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

Transcripts

mico --json meetings transcript MEETING_ID --limit 200 --offset 0

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

mico --json doctor

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:

mico meetings export MEETING_ID --format markdown --output meeting.md
mico meetings export MEETING_ID --format json --output meeting.json

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.