anarlog

Source excerpt starting at line 1.

1# CLI commands2 3Use `--json` for agent-readable output.4 5Linux Flatpak installs this command as `anarlog-cli`; use that name instead of `anarlog` in the examples when that is the command on PATH.6 7Account authentication works on headless systems:8 9```bash10anarlog auth login11anarlog --json auth status12anarlog auth logout13```14 15For `auth login`, give the printed URL to the user. They may open it on another device, sign in, choose **Copy URL**, and paste the resulting `anarlog://auth/callback` link into the hidden prompt. Never ask the user to paste that callback link into chat or expose it in command arguments because it contains account tokens.16 17On Linux, sessions use Secret Service when available and otherwise use the desktop-compatible local auth file with mode `0600`. With `--json`, `auth login` prints the URL to stderr and reads the callback from stdin.18 19```bash20anarlog --json doctor21anarlog --json meetings list --query "planning" --limit 20 --offset 022anarlog --json meetings --source cloud list --query "planning" --limit 20 --offset 023anarlog --json meetings --source auto get MEETING_ID24anarlog --json meetings get MEETING_ID25anarlog --json meetings note MEETING_ID --kind note26anarlog --json meetings note MEETING_ID --kind summary27anarlog --json meetings history MEETING_ID --limit 20 --offset 028anarlog --json proposals list --meeting MEETING_ID29anarlog --json proposals create --meeting MEETING_ID --kind summary --content "Replacement markdown"30anarlog --json proposals show PROPOSAL_ID31anarlog --json proposals decline PROPOSAL_ID32```33 34`proposals create` stages a pending edit. Do not claim the meeting changed. A human applies or declines it in the Anarlog desktop app.35 36Meeting commands default to `--source local`. `--source cloud` reads hosted snapshots using `anarlog auth login`; `--source auto` uses Cloud only when the local database is absent. Cloud access is read-only, so proposals remain local.37 38`doctor` exits with status 1 when its response contains `ready: false`.39 40Read transcripts in bounded word pages:41 42```bash43anarlog --json meetings transcript MEETING_ID --limit 200 --offset 044```45 46JSON success responses contain `schema_version`, `command`, `data`, and optional `pagination`. Continue from `pagination.next_offset` only when more context is necessary.47 48Export is intended for an explicit user request to save or transfer a complete meeting:49 50```bash51anarlog meetings export MEETING_ID --format markdown --output meeting.md52anarlog meetings export MEETING_ID --format json --output meeting.json53```54 55Export refuses to replace an existing file. Pass `--force` only after the user explicitly approves overwriting that exact path.56 57Global database overrides:58 59```bash60anarlog --db-path /path/to/app.db --json meetings list61anarlog --base /path/to/anarlog-data --json meetings list62```63