Your AI forgot who she loved by chapter 12
Green eyes in chapter 12. Brown eyes for 40,000 words. The model didn't get dumber. Your story outgrew the chat window.
A writer in Bangalore sent a screenshot at 1:14am IST.
Chapter 12. The AI reintroduced the love interest like a stranger at a wedding.
Green eyes.
She had brown eyes for forty thousand words.
Here's the part that makes people mad in writing Discords:
The model did not get dumber between chapter 3 and chapter 12.
You asked a chat window to be a warehouse.
A novel is a warehouse of decisions. Who knows the secret. Who is lying. Whether the knife is still in the drawer. What the town is called in book two.
ChatGPT is a brilliant intern who leaves after every meeting and loses the whiteboard. You will re-brief them forever and call it a workflow.
Old novelists had a boring name for the fix: a story bible. Not a mood board. Ops. Names. Scars. Lies. Open threads. Magic that costs something, or doesn't.
If the AI cannot see that, it is writing fanfiction of your own book. Scrivener users know this as manual index cards. Notion users build character databases and then reorganize them instead of writing. I wrote that trap down.
The grown-up move: proposals only. You accept or reject. Canon moves when you say so. Bible next to the page.
Open the draft. One mean question:
If every chat thread died tonight, does the book still have one source of truth for the cast?
If the answer is "uh, the Doc?", you do not have a system. You have hope. Hope is a terrible co-author.
Story bible · How to keep characters consistent · Start free
Straight answers
- Why does ChatGPT forget my characters mid-novel?
- Context windows drop early decisions. A novel is a warehouse of names, scars, and open threads. Put canon in a story bible, not a chat transcript.
- What is story bible software?
- Ops for the book: names, relationships, lies, magic rules. Typewriter keeps the bible beside the manuscript so CoAuthor can see it and still knock before changing the page.