Skip to main content

Global syntax

--db-path takes precedence over --base. Without either option, the CLI uses Anarlog’s platform application-data directory and recognized legacy locations. The installed command is anarlog on DEB, AppImage, macOS, Windows, and Settings-installed builds.

Account commands

auth login prints a URL that can be opened in any browser, including one on another device. Sign in, choose Copy URL on the completion page, then paste the anarlog://auth/callback link into the hidden CLI prompt. The CLI verifies the session with Anarlog before saving it in the same local auth store as the desktop app. With --json, the login URL and instructions are printed to stderr. The callback URL is read from stdin. JSON appears on stdout only after login completes. On Linux, the CLI uses Secret Service when it is available. Headless systems without Secret Service fall back to auth.cli.json in Anarlog’s local application-data directory with permissions limited to the current user. The desktop app reconciles that file into Secret Service when it becomes available. On Windows, the CLI stores sessions with DPAPI in the desktop app’s secure auth file. auth logout removes the local session; it does not delete the Anarlog account. auth status reports the signed-in account and whether the current access token has expired. The stored refresh token lets the desktop app refresh an expired access token when it starts.

Meeting data sources

Meeting commands accept --source local|cloud|auto before their subcommand:
local is the default and reads Anarlog’s database on this computer. cloud reads the opted-in hosted snapshots using the account saved by anarlog auth login. auto uses the local database when it exists and falls back to Cloud when it does not. Set ANARLOG_SOURCE to choose the same behavior without a flag. All meeting read commands support all three sources. --base, --db-path, and doctor apply only to local data. Proposals and anarlog mcp remain local because hosted Cloud access is read-only.

Meeting commands

Proposal commands

These commands insert or inspect staged edits. They do not apply the edit to the meeting. Apply happens in the desktop app.

JSON response contract

Successful --json responses contain: Pagination includes offset, limit, returned, optional total, and optional next_offset.

Doctor command

Checks the resolved database path, read-only access, and required schema without changing data. It exits with status 0 when ready is true and status 1 when ready is false.

MCP command

Starts the local MCP server over stdio. Meeting reads are idempotent. Proposal tools stage or decline pending edits without applying them to the meeting.
Do not write other output to the server’s stdout. Anything else written there corrupts the MCP stdio protocol stream.

Help and version