NovelAI chat memory: context, memory fields, and lorebook continuity
NovelAI gives writers structured tools such as Memory, Author's Note, and Lorebook entries. A chapter summary helps those tools stay focused on the current story state.
NovelAI describes Lorebook entries as supplemental information added to context when their conditions are met. Memory, Author's Note, recent story text, and lore entries can all compete for room in the generation context.
Use those fields for durable guidance, while a concise chat or story summary records the evolving chapter state that should not be left to a long raw history alone.
Signs it is time to make a continuity note
A key event from an earlier chapter stops shaping the next generation.
The Memory field is becoming a collection of old and new facts without a clear current state.
A lorebook entry explains the world but not the latest scene outcome.
A practical NovelAI preservation workflow
Keep durable world facts in the appropriate NovelAI memory or lorebook structure.
Copy the current story or chat section to thredly for a summary of characters, chronology, established facts, and the next objective.
Refresh the working summary at chapter breaks and move only genuinely lasting facts into permanent fields.
thredly is independent of NovelAI. It does not read NovelAI chats automatically. Copy a conversation section or use a native export when available, then paste or upload the text through thredly's supported web workflow.
What a useful handover should retain
Character identity, personality, voice, and any user persona details that still matter.
Names, relationships, boundaries, promises, preferences, and corrections that supersede earlier information.
Important story events, locations, dates, running jokes, unresolved plot points, and the current objective.
A short instruction for the next session that states where the conversation should resume.
What is the difference between NovelAI Memory and a Lorebook?
NovelAI's documentation describes lore entries as supplemental context that can be activated by conditions. Memory and other fields provide different context layers. A current chapter summary complements those layers.
Should I put every story event in a Lorebook?
No. Reserve lore for durable, reusable information. Use a short current-state summary for the evolving story arc.