Omniscio

Flashcards

Spaced-repetition flashcards for learning and retention, shipped as a plugin with its own sidebar tile: review cards on an FSRS schedule with one-key grading, skip or snooze a card, undo a grade, cram a pack ahead of schedule without disturbing that schedule, see any card's stats, and work with AI study sessions from the app's standard Sessions list, all stored on your computer.

On this page

What it is

Spaced-repetition flashcards for learning and retention. Flashcards is a first-party plugin in Omniscio that ships built into the app (it is turned on in Settings → Plugins, and the built-in copy always wins over a Marketplace one): the UI is a self-contained webview under src/plugins/flashcards/ and reaches core services through a typed bridge (window.AgentMC.flashcards). Backend (FSRS scheduler, Anki .apkg importer, media store, task-system integration, migrations, tables, CLI routes) STAYS in core so the data model + queries are shared with any future in-core consumer (e.g. an LMS meeting-intel handshake).

The user opens the plugin from its sidebar tile ("Flashcards"). Each pack holds cards; each card has a front + back (+ optional pasted images), a scheduling blob, and provenance (manual, anki-imported, ai-generated, or from a Courses lesson).

Where to find it

Flashcards has its own tile in the app sidebar, Flashcards. It ships built into the app and updates with the app; turn it on in Settings → Plugins (1.7.1 is the version with the screen described here). It runs on the desktop app; on a phone the app shows its usual desktop-only notice with the AI sessions button.

Opening it gives one left column, the app's own, with the standard toggle at the top: Flashcards | Sessions. Flashcards draws no sidebar of its own any more.

  • Flashcards lists Today (with how many cards are due, or "Caught up"), All cards (with the card count), Leeches (how many to fix), Stats (retention, a 30-day review heatmap, a 7-day forecast and your streak), Trash, then every pack with its due count. Each row's label is drawn by the app in your language with the number kept — "12 due" in the accent, "Caught up" in green, "3 to fix" in amber — and a row with nothing to say carries no label. Clicking an item opens it on the right. The list follows your packs as they change.
  • Sessions is the app's standard session list for Flashcards: the AI study sessions started from a pack, a card or the + New button, never your other sessions. Its suggested prompts include "Quiz me on what's due", "Make cards from my notes" and "Fix my weakest cards".

On an older app that cannot show the Flashcards list in its column, the top bar carries a small Today · All cards · Leeches · Stats · Trash switcher instead, and the packs are on Today.

The top bar is slim: the page title, then Search (F), Make cards (R) and New card (C), then small icon buttons for Import from Anki (any time, not only on a fresh install), Import CSV (V) and Keyboard shortcuts (Q).

The whole screen follows the app's text size: Ctrl+= and Ctrl+- (or the Text Size setting) grow and shrink Flashcards along with the rest of Omniscio. It uses the app's own type scale, quiet borders and rounded cards, and the accent colour only for the main button and due counts.

Today

Today is one quiet column: the date, then one headline in large type — "87 cards due", "1 card due" or All caught up — with the estimated time and how many packs the cards are spread over under it, and one accent Start review button beside the name of the pack the review starts with. W and S still pick a different pack from the keyboard; those keys are not printed on the screen (hover a button to see its key, or press Q for the map). When nothing is due it says All caught up and when the next cards are due.

Under the headline sits your daily goal as one line and a thin bar: "23 of 50 reviewed", Goal met for today once you reach it, your streak at the right and an Edit control that opens the goal dialog. On an app without the daily-goal feature the goal line is absent and the streak shows as one line of its own. Below it is the Packs list: each pack with its card count and how many are due. Retention, the forecast and leeches live on Stats and Leeches, not on Today.

Under it, Packs lists every pack — the ones with cards due first — each with its name over a thin bar showing how much of the pack is due, and on the right a bold due count or ✓ caught up. Clicking a pack opens its page; the + beside the heading starts a new pack.

Import cards from a spreadsheet (CSV)

Import CSV in the top bar (press V) brings cards in from a spreadsheet. You can choose a .csv, .tsv or .txt file, or paste rows straight into the box.

  • The commas, tabs or semicolons are worked out for you — you never tell it which one the file uses.
  • Pick which column is the front and which is the back from two dropdowns, and the first five rows are shown with those two columns tinted so you can check the mapping before anything is written.
  • First row is a header is ticked when the first line looks like column names rather than a card. It is only ever a suggestion — tick or untick it and the counts update.
  • Also make a reversed card adds a second card for every row, with the back as the question.
  • Send the cards into a new pack (named after the file, and you can type a different name) or into an existing one.
  • The line under the dialog always says exactly what will happen — "124 cards ready · 3 rows skipped" — and that number is produced by the same code that does the writing, so it cannot drift. Import is disabled when nothing can become a card.
  • A row is skipped, and counted, when its front is blank, its back is blank, it has fewer columns than your mapping needs, or one side is longer than 8,192 characters. Truly empty lines are ignored rather than counted.
  • Importing is all-or-nothing: either the pack and every card land, or nothing does. Imported cards start with a fresh, unstudied schedule, and each one records that it came from a CSV file (with the file name) so it is never mistaken for a hand-written card.

Packs and All cards

Clicking a pack opens its page: its cards, Review N due, Cram (practise the whole pack now, below), Export CSV (below), Start session (an AI study session on that pack), rename / delete in a small menu, and a Type answers row whose Inherit / On / Off control sets this pack's type-the-answer override — Inherit shows the current global value in brackets and is the default. The global value itself is off until set; it can be changed with POST /flashcards/update-settings ({"typeAnswerMode":"on"} or "off"), the same way the plugin's other settings are changed, because the plugin has no settings screen of its own. All cards lists every card across your packs with each card's chance of being remembered right now, carries its own Export CSV, and lets F filter the list; clicking a row opens that card's stats. A new pack is created together with its first card in the card editor.

Taking your cards out as a CSV

Export CSV on a pack's page saves that pack's cards to a CSV file through your normal save box; the same button above All cards saves every card you have. The file is plain rows — front, back, cardType, pack — so it opens in any spreadsheet and reads back into Flashcards unchanged. Two things worth knowing:

  • Your text is copied exactly, character for character. A card that starts with = or - is written as-is. That is what makes the file import back unchanged; it also means a spreadsheet may treat such a card as a formula when you open it there, so prefer a plain text editor if you open a deck you did not write yourself.
  • Deleted cards are not in it, and neither are the cards of a deleted pack. An empty pack gives a file with only the header row.

An agent can pull the same text without touching the disk: POST /flashcards/export-csv returns {csv, filename, cardCount} for one pack ({"packId":"…"}) or for your whole library (no body).

Leeches

Some cards keep slipping away no matter how often you see them. Leeches (in the Flashcards column, under All cards) lists the cards you have forgotten after learning them — graded Again 6 or more times — worst first, with how many times each one slipped and the pack it lives in.

  • Rewrite with AI asks the AI for a clearer version of that one card and shows the change as a before/after: either the same fact asked more plainly, or the fact split into two cards when one card was carrying too much. Nothing is saved until you press Accept; Reject leaves the card exactly as it was.
  • Not a leech takes the card off the list. It comes back only if you forget it again after that.
  • A card with an image cannot be rewritten this way (the AI only sees text, and a new question beside the old picture would be worse than the card you had) — its button says so; edit that card by hand instead.
  • Accepting never changes a card's schedule or its review history. The card keeps its place in your reviews; only the words change.
  • The number that makes a card a leech is a setting (leechThreshold, default 6) and the Leeches page shows the value in force.

The rewrite runs on your own Claude plan when you are signed in, and falls back to a stored API key otherwise. It is one small call per card, made only when you press the button.

Tags

A card can carry tags — lowercase, at most 32 characters each and at most 20 per card. The card editor has a tag field that shows the tags already on the card as chips, suggests the tags you already use as you type, and adds one on Enter or a comma. Card rows show up to three tags and count the rest.

All cards puts every tag in use above the list; picking one narrows the list to it and offers Review this tag, which opens one review across every pack for the cards carrying that tag that are due now. The review header names the tag.

Tags belong to the card, so editing a card's text, type or images leaves them alone. Deleting a card keeps its tags while it sits in Trash — they stop counting anywhere in the app — so restoring it brings them back; they are removed for good only when the card is (Delete forever, Empty trash or the daily sweep). The set also moves with your data: tags are included in a backup and in "download my data", and are erased with your cards.

Every tag control hides itself on an app version that does not have the tag routes, so an older install shows the panel exactly as it was before tags existed.

Trash

Deleting a card or a pack only hides it — the row stays in the database and Trash (an item in the Flashcards column) lists it for as long as the app's data-retention window (30 days by default), showing when it went and how many days are left. Each row offers Restore and Delete forever; the header offers Empty trash. Both deletions ask first, and the dialog opens on Cancel.

Restoring a pack brings back the pack and every deleted card in it, so nothing is ever left stranded: a card deleted a day before its pack is reachable only through that pack, and restoring the pack is how you get it back. Restoring a card from a pack that is itself deleted does the same thing. A restored card comes back with its tags, whether it was deleted on its own, in a multi-card delete or with its pack. If a live pack has taken the restored pack's name, the restored one comes back suffixed ("Spanish (2)") and the app says so.

Items older than the window disappear from Trash and are removed for good by the daily sweep, which runs on the app's own in-app scheduler — never a Windows task — and never touches a live row.

For agents: the screen's views

SubView (store/pack-slice.ts) routes the main area; every member must have a navigation target, which tests/unit/lint/35/flashcards-subview-reachable.test.ts enforces. The views are reached from the items the island publishes to the app's column (useHostSidebar + lib/host-sidebar.ts: ids view:today, view:all-cards, view:leeches, view:stats, view:trash and pack:<id>, opened by the host's navigate command) or, on an older app, from the top-bar view switcher. The stats dashboard (DashboardTile) is the Stats item and tests/unit/plugins/flashcards-dashboard-tile-reachable.test.tsx keeps it reachable.

How it behaves

Reviews are scheduled by an FSRS spaced-repetition scheduler that runs inside the app, and your cards and reviews live in your local database — no account and no cloud. (Start session, below, opens a Claude session, which uses your AI like any other session.) A pack's counts are worked out when the page is read rather than stored, so they are never stale; media attached to a card is held in a local store and survives a re-import.

Daily goal, streak and reminder

Turn the daily goal on in the goal dialog (on by default, 20 cards) and Today shows a bar of today's reviews against it; the goal streak counts the consecutive local days that reached it, and a day still in progress neither counts as met nor breaks the run. The window is 365 days. Going past the goal keeps the bar full. Turning the goal off hides the bar and leaves your review history untouched - the Stats dashboard keeps its own "days with any review" streak, which is a different number.

The reminder is a separate switch with a time (24-hour, default 09:00, off by default). Once a day, at or after that local time, the app raises one inbox card naming how many cards are actually due right now ("12 cards due - review now.") whose Open Flashcards button opens the panel. It posts nothing when nothing is due, never posts twice in a local day, and stays silent while the plugin is switched off. Both the goal and the reminder are saved on the Flashcards settings row, so they survive a restart.

Reviewing

  • The card: the review screen is three bands. A slim header carries an ✕ that exits (Esc), the pack name, "5 of 12", a keyboard-shortcuts button and a hairline progress bar; the app's own top bar is not shown while you review. The card fills the middle and is the only part that scrolls. The answer bar is fixed to the bottom, so the grade buttons never leave the window however long a card is. A quiet caption above the card names its state (New, Learning, Review, Relearning), its type and when you last saw it. The card has no box around it: the question sits large and centred (code and fill-in-the-blank cards stay left-aligned) with one accent Show answer button under it that prints its key, Space; on a very long question that button stays in view at the bottom of the card area. Show answer or Space turns the card over with a quick fade: the back repeats the question small and shows the answer and any note below a divider, in one size. A fill-in-the-blank card shows the gap, then the missing word; a card with a picture shows the picture; a code block shows as code; a very short front (a single word) shows large.
  • Type the answer (optional): when the mode is on for the pack, a text box sits under the card front. Type the answer and press Enter to reveal. The back then shows your answer beside the expected one, with the characters that differ marked on each side — case, a leading or trailing punctuation mark and stray surrounding spaces are ignored, so PARIS. against Paris shows no marks at all. The grade that answer suggests is highlighted on the buttons: Good for an exact match, Hard for a close one, Again for a wrong one — never Easy, and nothing is graded until you press a button. A fill-in-the-blank card asks for the hidden word (every blank, in order); a card with nothing to type asks nothing and reviews as before. In the first three reviews, where only Forgot and Remember exist, the suggestion names whichever of those two it means. While the box has focus no shortcut fires, so you can type spaces and numbers; leave it (Tab, or Enter to reveal) and the shortcuts work again.
  • Grading: the four grades — Again, Hard, Good, Easy — sit in one row of equal buttons in the answer bar, on both sides of the card. Each button always prints its key (1, 2, 3, 4) and when the card would come back. The buttons share one plain look; once the answer is showing, Good (or the grade your typed answer suggests) takes the accent, so there is exactly one highlighted button on the screen at a time. One row of quiet labelled buttons under the grades holds Undo, Skip, Snooze, Stats, Edit and Ask AI; the snooze menu opens upward over the card. You can grade before flipping, and it counts exactly like grading after. The time to answer is measured from when the card appeared.
  • Your first three reviews show two buttons instead, Forgot (1) and Remember (2), and the caption above the card carries a small chip counting the sessions left before the four grades appear.
  • Skip (S) moves the card to the end of this review. Nothing is saved.
  • A card deleted elsewhere while you review (another window, an agent) is dropped from the review when you grade it, with a note, and does not count as graded. If closing a finished review fails, you go back to Today with a message; your grades are already saved.
  • Snooze (W) opens a menu — 1 hour, Tomorrow, In 3 days, Next week, or Pick a date (keys 1–5). The card's due date moves to that time and it leaves today's review. Snoozing records no review and changes nothing else about the card. A time in the past or more than a year out is refused.
  • Undo (Z) takes back the last grade in this review: the card's schedule goes back to what it was, that grade's record is removed, and the card comes back showing its answer so you can grade it again. Undo works within the current review, and with nothing to undo it says so. A grade already counted toward a pack's study task stays counted.
  • Card stats (D), or the Stats button under the grades, opens a side panel: the chance you would remember the card right now, reviews, times forgotten, difficulty, memory strength, average answer time, when it was added, when it is due next and what Good or Easy would do, a memory curve with a "Now" marker against the 90% goal, and the last 50 grades. Looking at stats never changes the card. If the stats cannot load, the panel says so with Try again.

Cramming a pack

Cram on a pack's page studies that pack now, whether or not anything is due — the whole pack, weakest first. It is practice, not study: a grade in a cram review saves nothing, so every card keeps the schedule it had before — no grade moves a due date, no review is recorded, and the heatmap, streak, retention and answer-time figures are untouched.

  • The queue is every live card in the pack, weakest first by your chance of remembering it right now, so the cards closest to slipping come first. A card you have never reviewed counts as the weakest of all.
  • Grading works exactly as in a review — the same four grades, the same hotkeys — but the buttons show no next interval, because nothing is being scheduled. Skip, Snooze and Undo behave as they do in a review; snoozing still moves the real due date, because that is what snoozing means.
  • The end screen is a cram summary: how many you remembered, and a plain line that no grades were saved. Cram again (Space) starts another pass over the same pack. (A normal review ends on Session complete: a green check and "10 of 12 remembered", your streak, the daily-goal bar, then Cards to look at again — every card you graded Again, named by its question, each with an Explain with AI button that starts a study session on that card. The due count is read again after the review. While cards remain it says how many and highlights Keep going (Space) beside Done for today (Esc); when none remain it says All caught up and when the next cards are due, and highlights Back to Today (Esc) beside Review more (Space). If the count cannot be read it says so and makes no claim either way.)
  • Cram has no keyboard shortcut of its own; it is a deliberate, occasional action. It counts as no review session, so your review count does not move.

Keyboard shortcuts

Every shortcut sits on the left half of the keyboard. None fires while you are typing in a field, while a key is held down, with Ctrl, Alt or ⌘ held, or while a dialog is open. Q (or ?) shows the list with a keyboard map. Only the grade buttons and Show answer print their key on screen (1 to 4, and Space); hover any other button and its tooltip names the key.

Key What it does
Space Start review · show the answer
1 2 3 4 Again · Hard · Good · Easy (1 and 2 in the first three reviews)
S Skip (reviewing) · move down (lists)
W Snooze, then 1–5 to pick a time (reviewing) · move up (lists)
D Card stats
Z Undo the last grade
E Edit the card
A Ask AI about this card
R Make cards — draft cards from a passage or a link
F Find
T · B · C Today · All cards · Create a card
X Select cards in a list
Q Keyboard shortcuts
Esc Back · close

Make cards from a passage

Press R, or the sparkle in the top bar, to open Make cards. Paste a passage — a note, an article, anything you want to learn — or paste a link and Omniscio reads the page for you. Choose the pack the cards should go into and roughly how many you want, and press Draft cards.

You then get a list of drafts to go through. Every draft starts Kept; press a draft's Kept button to leave it out, Edit to change either side, or Drop to remove it. The button at the bottom counts what you kept — it reads Save 6 cards — and nothing at all is written until you press it. Leave without saving and the pack is exactly as it was.

A card you keep carries a quiet note that it came from AI, so you can always tell later where a card came from. If the passage was long, only its first part is read, and if you ask for fewer cards than the AI drafts, the first ones are kept.

Making cards uses AI tokens on each press of Draft cards — it is the one part of Flashcards that spends anything on an AI model. A daily limit protects you from a runaway bill, and the spend shows up under Stats → Spend like any other AI feature. Everything else in Flashcards — reviewing, importing, editing, stats — is free and local.

Maths and code on a card

A card's front and back can carry formulas and code, and both are drawn properly wherever a card is shown — in a review, in the card editor's preview while you type, and (with the markup stripped, on one line) in the card list and the card-stats header.

  • Formulas go between single dollar signs for inline maths ($x^2$) and double dollar signs for a centred block ($$\frac{a}{b}$$). They are set with KaTeX, so fractions, roots, sums and Greek letters look like a textbook rather than like source.
  • Code goes in a fenced block with a language name after the backticks — ```python, ```sql, ```bash — and is coloured by highlight.js. Around twenty common languages are built in; an unknown or missing name still shows the code, just without colours.
  • A formula the app cannot read is shown as you typed it, in a quiet red, with the rest of the card intact — a typo never blanks the card or stops the review.
  • A price is not a formula. The closing dollar of an inline formula must not be followed by a number, so "Tickets cost $540–$1,800" stays a sentence while $540$ stays maths.
  • One known limit: if a fill-in-the-blank gap sits inside a formula ($\frac{{{c1::a}}}{b}$), the two halves cannot be joined back up, so that formula shows as its source text instead. A blank between two separate formulas works normally.

Start an AI study session on a pack

On a pack's page, Start session opens a Claude session loaded with that pack. It lands in Flashcards' own project (__plugin_flashcards__), so it shows in the column's Sessions list beside the ones started there; Ask AI on a card (A) does the same. If Tasks is turned on, Omniscio also adds a task called "Review Flashcards Pack: pack name (number cards)" to your Tasks Inbox and links the session to it. The number is how many cards the pack held when you started.

After that, each card in the pack that you grade counts toward the task, once per card. While the task is open, the pack page shows "Current session: X/Y cards graded". When you have graded as many cards as the task started with, Omniscio marks the task done for you and the line goes away.

With Tasks turned off, Start session only opens the Claude session. No task is made, and the progress line does not appear.

Cards from a course

When you finish a lesson in Courses, that lesson's flashcards can join your own deck, in a pack named after the course (" (2)" is added if you already have a pack with that name). Each course card arrives once: finishing or reopening the lesson again adds nothing new, and a course card you delete from the pack does not come back. No pack is made for a lesson that has no cards. The cards are ordinary cards from then on: they are scheduled, reviewed and counted like any other, and they stay on your computer. Flashcards can never stop a lesson finishing — if the deck write fails, the lesson stays completed and the cards are simply not delivered.

You can also make your own cards from a lesson. Select text while reading a lesson in Courses, right-click and choose Make a flashcard from this: the front is prefilled with the selection, you write the back, and the card goes straight into your own deck in the course's pack — whether or not you have finished the lesson. The same dialog lists the cards you have already made from that lesson, with Edit and Delete on each. A card you make this way is private to you: no other learner sees it, it is not course content, and it never changes the course's numbers. If you removed the course deck, the card waits with that deck and comes back when you restore it.

Flashcards does not read your sessions, and the only thing it adds to Tasks is the study-session task described above; for the notes-and-memory side of Omniscio see Global memory.

Last verified 2026-11-12