AI in Wyrdli
The places AI shows up in Wyrdli: the Session recap, the in-editor writer, and Template-driven generation. What each one does, and what stays human.
Ultimo aggiornamento 22/08/26
Wyrdli · Aiuto e documentazioneThe places AI shows up in Wyrdli: the Session recap, the in-editor writer, and Template-driven generation. What each one does, and what stays human.
AI in Wyrdli isn't a chatbot in the corner. It shows up in a handful of specific places, each doing one job, and everywhere else the app is hand-driven. Knowing which surface does which job is most of the trick to getting useful output.
There are three places AI runs in Wyrdli: the Session recap, the in-editor writer, and Template-driven generation when you create a new entity. They share one rule: every output lands as a proposal you read, edit, or throw away. Nothing AI produces is written into the Campaign until you click through it.
That's the contract. Everything below is how each surface honours it.
The recap turns a finished Session's Transcript into a written record. You click "Generate Recap" on a Session that has a Transcript, and the recap produces three things:
A narrative summary of what happened, in prose.
A list of events: the concrete things the recap noticed (a strike landed, an NPC met, an Item changed hands).
A structured debrief: open questions the recap thinks the next Session will need to answer.
The recap is the largest of the three tools, and the one that does the most work in one click. It runs once per Session, on demand, and the result attaches to the Session page. You can re-run it; the Transcript doesn't change, the recap is regenerated from it.
Every long-form editor in Wyrdli (Scene narrative, Location description, Session notes, Secret writeup) supports two inline slash commands:
/write drafts a fresh paragraph from a short prompt you type after the slash.
/expand takes what you've selected (or the paragraph the cursor is in) and lengthens it.
You type the slash command inline, the writer drafts text in place, and you accept or discard the draft. The cursor lands where the draft ends, so you can keep typing.
The third surface is more architectural, and it's how AI actually learns the Campaign's voice. When you create a new entity (a new NPC, a new Location, a new Scene), the active Template for that kind of entity becomes the starting content of the new entity's description.
A Template is a structured document. It has headings you define ("Background", "Appearance", "What they want", "What they fear", "Threats they pose"), and underneath each heading, the Template author writes italic instructions to the AI describing what that section should contain ("describe their physical features in two sentences", "name one secret they're hiding from the party").
When you ask the AI to fill the Template, it replaces each italic instruction with generated content matching the hint. The italic instructions don't survive in the output, they exist only to guide the generation.
A good Template is a prompt-engineering document. The headings shape what an entity looks like in this Campaign's voice; the italic hints shape what the AI writes in each section. Writing good Templates is how you teach the AI the Campaign's tone.
Every piece of AI output in Wyrdli lands as a proposal: a recap you read before keeping, suggestions you accept one at a time, a paragraph you can throw away, a Template draft you edit before saving. The GM (or the author) decides what survives.
There's no autonomous loop. The bot doesn't write into the Campaign on its own, it never "improves" your text in the background, it never publishes anything that hasn't been clicked through. The story stays yours; AI is a fast first draft on a handful of specific tasks.