The Codex

The campaign remembers itself

Take notes while you play. Mark the session played, and the tome can read them back to you as proposals — new places, quests, threads, and people. You decide which ones become canon.

During play

Notes that autosave while you run the table

A full-width editor sits in the active session, saving as you type with a status indicator so you never wonder. When the night ends, mark it played with a title — and the tome gets to work on what you wrote.

  • Autosaves while you play, with a save indicator
  • Mark as played with an editable title
  • Optional AI review polishes notes against your own sources
Advisory, always

Nothing becomes canon until you apply it

Extraction proposes; it never writes. Every operation arrives in a review queue — Processing, then Pending Review — and you accept it, edit it, or dismiss it. Your campaign changes on your click, not the model's.

  • Accept, edit, or dismiss each proposed change
  • A notification tells you when a review is waiting
  • Nothing touches campaign state before you apply
The record

Places, quests, threads, and people

The codex holds locations — with only ever one marked current — plus quests, plot threads, and a roster of NPCs carrying statuses and relationships. Ties are directional: that Ilmater's priest trusts the party says nothing about what the party thinks of him.

  • Locations, quests, and plot threads
  • NPCs with statuses and portraits
  • Directional relationships between NPCs and the party
Ask your own history

"What happened to Elturel?"

Played-session recaps are handed to Sage as citeable sources alongside your rulebooks. Ask about a place, a person, or a promise the party made four months ago, and the answer comes back from your table's own record.

  • Recaps cited like any other source
  • Ask about your lore, not just the rules
  • Your history — not the internet's
The table is waiting

Pick up the pen. Put down the spreadsheet.

Open your tome