Summary
A review done in chat still counts as a review, because the ease goes back onto the cards.
The loop closes: due cards come out, you answer them in conversation, update_cards marks them answered and adjusts ease, so the scheduler stays authoritative rather than drifting away from what you actually studied. Card creation is the strict part — the formatting rules are HTML-only and spelled out down to <br> for line breaks, so a card composed in markdown will not come out looking the way it read.
What it is
A server over an Anki collection that hands out due and new cards, records answers against them, and creates cards.
What you get
- A given number of cards that are due for review, handed over for quizzing
- New and unseen cards pulled the same way, for working into a fresh deck
- Answers written back so the cards are marked answered and their ease updated
- New flashcards created with a front and a back
Requirements
A running Anki with the collection you want to review, reachable by the server. Card content must be HTML: line breaks as <br>, code inside <pre> with inline styling, lists as <ol> — markdown is explicitly not accepted.