Anarlog

Prefer local Anarlog data when the agent can access it. Use OAuth-connected Cloud MCP when running remotely or when local data is unavailable. Meeting reads are safe. Use local proposal tools to stage edits, or local import tools to create a meeting from an explicitly requested recording.

Choose a source

1. Honor an explicit local-only or Cloud request. Do not silently switch its source.
2. Otherwise, prefer a connected local MCP server. If shell access is available, select the CLI executable available on PATH: anarlog-cli on Flatpak, otherwise anarlog. Use that executable for every CLI command below, including the --json doctor readiness check. Read with the selected executable and --json meetings --source local list when ready, even if Cloud MCP is connected.
3. When running remotely without the user's local database, or when the CLI or database is absent, use connected Cloud MCP: list_meetings, get_meeting, get_meeting_transcript, and get_recurring_meeting_history. If MCP is unavailable but CLI login is available, use the selected executable with --json meetings --source cloud list for the same hosted snapshots.
4. A local database compatibility, permission, or operation error needs to be reported; do not hide it by switching to Cloud. An empty local result does not mean the database is unavailable. If the requested meeting is missing, an already-connected alternate source can fill the gap unless the user restricted the source. Identify that source and keep the meeting's subsequent reads on it.
5. Local reads need no Cloud login, Pro subscription, or completed sync. If neither source is available, offer local CLI installation for an agent on the user's computer, or Cloud API & Connectors plus OAuth for remote access. Do not install software or enable Cloud uploads unless the user asks.