Skip to content

Session recaps you can read at the table without editing them first

The recap is the highest-value thing a DM writes and the first thing that gets skipped. This generates one from the session you already recorded.

Generated from the transcript, not from your notes

A recap job runs automatically once a session finishes transcribing. It reads the whole transcript and produces a summary aimed at being read aloud: what happened, what the party decided, who they met, and what was still unresolved when you called it.

Alongside the summary, recaps carry a set of extended sections — the structured detail that a bare paragraph loses. Characters and locations named in the recap are linked to the wiki entries they match, by canonical name or by alias, so a recap is a way into the wiki rather than a dead end.

No recording, but a transcript? A session captured some other way — Craig audio you ran through Whisper yourself, another transcription tool, a play-by-post log — can be imported as text, and the recap is generated from it the same way, along with the wiki entries. An import spends no transcription hours; it has its own monthly allowance instead. How importing a transcript works.

Recap or summary: what you get back

Both, from one job. The summary is the narrative: several paragraphs on what happened, what the party decided and where they stopped, with a longer scene-by-scene retelling beside it for when you need the detail. Around it, the session is broken into structured sections, so the things you look up later are not buried in prose:

  • Key events, in the order they happened
  • The characters involved and the locations visited, linked to the wiki entries they match
  • Quest progress, combat encounters and the decisions the party made
  • Treasure and rewards, and what the session revealed about the world
  • Open mysteries, and the cliffhanger you stopped on
  • Hooks for next session — what the party means to do next — which also carry into the app’s pre-session prep view

Setting the length and tone, and handing it to players

Length, tone and emphasis are yours to set when you regenerate. Length is Brief, Standard or Detailed, and Brief asks for two or three short paragraphs instead of the longer default. Tone is Neutral, Dramatic, Gritty, Humorous or Epic. Emphasis tilts it toward any of combat, roleplay, exploration, plot, loot or lore without dropping the rest, and the version history shows which settings produced each version.

Getting it to the table takes one click. The player copy takes the summary, key events, memorable moments and the next-session teaser, and leaves GM-facing sections such as mysteries and decisions out, ready to paste into the group chat. For your own records, the recap and the full transcript download together as one document.

Regenerating never destroys what you wrote

You can regenerate a recap with a different length, tone or emphasis, and you can edit the summary by hand. Both are safe: every generation is stored as a new version, and the five most recent are kept.

This is deliberate and it was not always true. An earlier version deleted the existing recap before writing the new one, which meant a regeneration that produced something worse destroyed the hand-edited version permanently. Now old versions are pruned only after the new one is safely written, so a failed generation leaves your existing recap untouched. You can view the version history and restore any earlier version, which is copied forward as a new version rather than rewriting history.

Where the recap fits the rest of the campaign

Recaps feed the campaign timeline, which lays out every session with its recap snippet, up to five key events, and the wiki entities that made their first appearance in that session. For a campaign returning after a three-month break, that view is usually more useful than any single recap.

What this does not do

It cannot recap a session nobody captured. It needs a recording or a transcript: there is no way to reconstruct a session from nothing, and a recap generated from four bullet points would be fiction.

It does not know who said what. There are no speaker labels — the transcript a recap is written from is the words in order, not a script with a name in front of each line. The model works out who did what from what was said, a character named aloud or an action announced on someone’s turn, and it will sometimes credit the wrong character with a line or a decision. Check the attributions when you skim it.

It does not know what you intended. The model summarises what was said, so a plot thread you deliberately kept ambiguous at the table stays ambiguous in the recap — and a detail the party misunderstood is recapped as it was said, not as you meant it. Editing exists for this.

It is not a substitute for reading it before you read it out. Generated recaps are good enough to use with a skim, not good enough to perform sight-unseen.

If you have notes rather than audio and just want to see the shape of the output, the free recap generator takes pasted notes and needs no account — though a recap built from a page of bullet points can only repeat the bullet points. To write one yourself, how to write a session recap is a short method, and NotebookLM for D&D covers doing it with a general AI notebook.

Which plans include it

Included on every plan, including the free Adventurer tier, which gets 2.5 hours a month plus 3 one-time bonus hours at signup. Version history, regeneration and hand-editing are on every plan too. A recap from an imported transcript spends no hours; imports are metered separately — 2 a month on Adventurer, 10 on Dungeon Master, unlimited on Guild Master. There is also a free generator that works from pasted notes with no account at all, if you want to see the writing before signing up for anything.

Full pricing

The rest of what it does

All features