Docs and product site: takhoffman.github.io/ankicli

Standalone agent skill: bundled skills

Goal-driven study: learning plans

ankicli is a local-first Anki CLI for humans who want to install and supervise a safe, scriptable control surface for agent harnesses like Claude, Codex, OpenClaw, and custom automation.

Installed by humans. Operated by agents.

Supported platforms: macOS, Windows, and Linux.

License: AGPL-3.0-or-later.

Use ankicli when you want:

• a terminal-native Anki control surface that agents can drive safely
• a human-friendly install and verification path
• profile-aware local collection access
• explicit dry-run, confirmation, backup, and sync-preflight flows
• stable JSON output for automation instead of fragile desktop UI scripting

macOS and Linux:

curl -fsSL https://raw.githubusercontent.com/Takhoffman/ankicli/main/scripts/install.sh | sh

Windows:

irm https://raw.githubusercontent.com/Takhoffman/ankicli/main/scripts/install.ps1 | iex

Fallback package path:

pipx install anki-agent-toolkit

The PyPI distribution is anki-agent-toolkit; the installed command is still ankicli.

Run the human setup wizard first, then use JSON checks before handing ankicli to an agent:

ankicli --version
ankicli configure
ankicli --json doctor env
ankicli --json doctor backend
ankicli --json profile list
ankicli skill install --target codex

If you skip collection, sync, or agent skill setup, run ankicli configure later to reopen the same wizard.

Save your default Anki profile once, then normal commands can omit repeated --profile flags:

ankicli --json profile default
ankicli workspace set --profile "User 1"
ankicli --json workspace show
ankicli --json collection info
ankicli --json search preview --kind notes --query 'deck:Default' --limit 5
ankicli --json note add-tags --id 123 --tag review --dry-run

Human-facing workspace config lives under ~/.ankicli/workspaces/<name>/config.json. The active workspace is default, and you can add more named workspaces for different workflows:

ankicli workspace set --name travel --profile "Travel" --activate
ankicli --workspace travel --json collection info
ankicli workspace use --name default

Sync credentials are stored separately in the system keyring when available, with a platform-specific file fallback if no usable keyring exists.

For a fully explicit setup, use a collection path instead of a profile:

ankicli workspace set --collection /path/to/collection.anki2

• inspect profiles, collections, decks, models, tags, cards, and media
• search and preview notes/cards before changing anything
• mutate notes and card state with explicit dry-run and confirmation paths
• create local backups and run explicit restore flows
• inspect auth state and run sync preflight before real sync work
• run local tutor-style study sessions from the terminal

• Prefer --json for scripts and agents.
• Use --dry-run first on write-capable commands.
• Prefer saved workspace config for day-to-day use: ankicli workspace set --profile "User 1".
• Prefer --profile for normal local usage and --collection for explicit low-level targeting.
• Use sync status as the safe preflight before running a real sync.
• Sync is not backup. Use backup create or the built-in auto-backup flow when rollback matters.
• Riskier local python-anki writes create an automatic pre-mutation backup unless you pass --no-auto-backup.
• Real note delete, card suspend, and card unsuspend require --yes.

• Product site: takhoffman.github.io/ankicli
• Bundled skills: bundled skills
• Learning plans: learning plans
• Recipes: recipes
• CLI guide: cli guide
• Common tasks: common tasks
• Quickstart: quickstart
• Install guide: install
• Profiles and collections: profiles and collections
• Sync and backups: sync and backups
• Study mode: study
• Troubleshooting: troubleshooting
• OpenClaw plugin adapter (internal/dev): openclaw plugin

Every major docs page is designed to be readable by humans and easy to copy into an LLM chat.

ankicli is licensed under AGPL-3.0-or-later. It depends on the upstream Anki runtime, which is also AGPL-licensed. See LICENSE.

The top-level README is intentionally product-oriented. Contributor and backend-contract detail still exists, but it lives in deeper docs and repo files:

• CLI and backend contract: docs/spec.md
• Release/install workflows: product site
• Source and workflows: repository

Common contributor commands:

uv sync --extra dev --frozen
PYTEST_PLUGINS=ankicli.pytest_plugin uv run pytest -c pyproject.toml -m "unit or smoke" --proof-report /tmp/ankicli-proof-report.json
uv run ruff check .
uv build
uv run pytest -m distribution