Generate a session recap
Once the Transcript is in, click Generate Recap and step through the AI's narrative, events, and debrief. Every part of the recap is editable before it lands.
Ultimo aggiornamento 12/09/26
Wyrdli · Aiuto e documentazioneOnce the Transcript is in, click Generate Recap and step through the AI's narrative, events, and debrief. Every part of the recap is editable before it lands.
The Session ended an hour ago, the players are off the call, and you're sitting in front of the Session page with the Transcript fully processed. You could write the recap yourself. You'd rather have a first draft to push against, so you can spend your evening on the bits that mattered instead of typing the connective tissue.
That's what the recap is for. The AI reads the Transcript, the Campaign's existing entities, and the active arcs, and it produces three things: a narrative summary you can post in the play channel, an events list of what actually happened, and a debrief with structured notes.
A Session's Transcript is finished and you want the narrative writeup, the event log, and the debrief notes.
Open the Session's detail page. The Transcript section shows progress; the "Generate Recap" button is disabled until the Transcript is complete.
Once the Transcript is in, click "Generate Recap". The AI reads the Transcript against the Campaign's context.
Wait a moment while the recap is composed. Longer Sessions take longer; a three-hour Transcript usually finishes in under a minute.
Review the three tabs: Recap (the narrative summary, written in a voice you can post to Discord), Events (a structured list of what happened, who was there, what changed), and Debrief (the notes you'd otherwise write yourself).
Edit anything that needs editing. Every part of the recap is editable: tighten a paragraph, fix an attribution, delete a moment that didn't land, add the thing the AI missed.
Save. The recap is now attached to the Session and shows up in the Campaign's history.
Recap generation only runs from the Session page. There isn't a parallel path from the Campaign tab or the header. The AI needs the Session's Transcript as input, and the Session page is where the Transcript lives.
You can re-generate if the first pass missed the mark. The current recap is overwritten when you re-generate, so copy anything you've already edited into the description first.
You can post the Recap to Discord from the Session page once you're happy with it. The play channel gets a formatted version of the Recap tab, which is the part written in a voice the players will recognise.
The three tabs each do a different job, and the editing pass should treat them differently.
Recap (narrative). Written for the players. Post-and-forget shape: a paragraph or two of what happened, in-character flavour, the kind of thing that opens the next Session well. Edit it like you'd edit a blog post.
Events (structured). Written for you. A list of things-that-happened, attributed to who was present, with the Clues found and Threats triggered. The Campaign's running log reads this list. Edit it like a record: factual, terse, complete.
Debrief (notes). Written for the next prep session. Open threads, players' unspoken questions, the moments the GM made a call that they want to revisit. This is the tab to read before you start prepping the next Session.
The recap is a first draft, not a deliverable. The AI doesn't know which moment your table really laughed at, or which one is going to matter for the arc later. Five minutes editing is what turns the draft into something worth posting.