Using AI as a GM: what helps and what gets in the way

We asked a community of GMs who play with AI how it's going. Some have run solo campaigns with a chatbot as GM for most of a year. Others tried it and walked away. Their answers point the same way: AI is good at remembering and drafting, and bad at taking over the parts that make you the GM.

What goes wrong

Prep you didn't make is prep you don't know
One GM let AI write their scenes and found themselves less ready at the table. They hadn't built the scenes, so they couldn't improvise around them. They also caught themselves asking a chatbot questions they could have answered on their own.
Everyone is too nice
A chatbot running the whole game tends to agree with you. NPCs are friendly, plans work, and the world rarely pushes back.
Threads go missing
Over weeks of play, details drift. Long-running plot threads fade, and items quietly vanish from the party's packs.
The workarounds pile up
GMs who make it work for months do a lot by hand: a summary document at the end of every chat, pasted into the next one, and rules corrections like stopping the AI from rolling the player's dice too.

What works

You set the direction, AI fills in
One GM drafts lore, NPCs and dialogue with AI as a back-and-forth. They give a rough outline, let AI fill the gaps, then review and push back until it's right. Because they stay in the conversation, they still know their world.
Give AI a smaller job
One builder only lets AI voice the NPCs, while the game itself keeps track of the world. That alone fixed the yes-man NPCs and the disappearing inventory.
Memory is the hard part
Another builder working on an AI-driven virtual tabletop said the real challenge wasn't storytelling. It was memory. An AI does fine when it has a record it can update and check.

A simple rule for AI at your table

  • Write the scenes you'll need to improvise around, or at least steer every draft
  • Let AI do the bookkeeping: who said what, what happened when, which threads are open
  • Check anything before it becomes canon
  • Keep each job small: one NPC, one summary, one question at a time
  • If you catch yourself asking AI something you could make up, make it up

Where Masterlens fits

Keeps the books for you
Masterlens reads your session notes, transcripts or recordings and keeps track of the characters, places, items and events in your campaign.
Drafts when you ask
Ask Masterlens to draft lore, an NPC or a backstory, and the draft builds on what's already in your campaign. Once you approve it, Masterlens knows it too, so later answers and drafts stay consistent with it.
You stay in control
Every update, from a session or a draft, arrives as a suggestion. Nothing goes into your campaign until you approve it, and you can edit anything afterwards, so a table joke or a bad guess never becomes lore.
Answers you can check
Ask "what did we promise the smith?" and get an answer that links back to the session it came from.
No summary docs to paste
The end-of-chat summary that GMs keep by hand is what Masterlens keeps for you, session after session.

Questions GMs ask

Can ChatGPT or Claude run a D&D campaign?
Some players run long solo games this way and enjoy them. Expect to steer it: ask for tougher NPCs, keep your own summaries, and correct it when it drifts from the rules or the story.
Will using AI make me a worse GM?
It can, if it does the thinking for you. Use it to draft under your direction and to keep records, and keep the creative calls for yourself.
Does Masterlens write my campaign for me?
Only the parts you ask for. Masterlens keeps track of what happened at your table, and when you ask, drafts lore or NPCs that fit what is already there. You review every draft before it is saved, and you run the game.