Memory Books turns parts of your SillyTavern chat into organized memory entries that can be recalled later.
The basic process is:
- Select part of the chat.
- Ask Memory Books to summarize it.
- Save the summary in a lorebook.
- Hide older chat messages to save context.
- Let the saved memories supply important information when it becomes relevant again.
This guide walks you through installation, your first memory, automatic memory creation, and the major features you may want afterward.
By the end of this guide, you should know how to:
- Install or locate Memory Books
- Open the Memory Books settings
- Choose where memories will be stored
- Choose which AI connection creates memories
- Mark a scene in the chat
- Create and verify your first memory
- Understand why chat messages may become hidden
- Enable automatic memory creation
- Choose between Memories, Clips, Topical Clips, Side Prompts, Consolidation, and Compaction
- Identify the first things to check when something does not work
Memory Books requires:
- SillyTavern 1.14.0 or later
- A working AI connection
- A model capable of following instructions and returning valid JSON
- Permission to install third-party SillyTavern extensions
The latest compatible SillyTavern version is recommended.
If you use OpenAI, Anthropic, Claude, OpenRouter, Gemini, or another Chat Completion connection, you can normally use your existing SillyTavern connection.
Memory Books includes a built-in profile called Current SillyTavern Settings. This tells Memory Books to use the connection and model currently selected in SillyTavern.
KoboldCpp, llama.cpp, TextGen, Ollama, and similar local backends may require additional setup.
Memory Books sends structured generation requests and expects valid JSON. Local backends generally work most reliably when exposed through an OpenAI-compatible Chat Completion endpoint.
You must also have a Chat Completion preset available in SillyTavern, even if you normally roleplay through Text Completion.
If you are not sure whether this applies to you, try the normal setup first. Investigate the local-model instructions only if memory generation fails.
Memory Books can use SillyTavern’s Chat Top Bar or Chat Top Info Bar extension to show a job queue.
The queue is useful for:
- Watching memory-generation progress
- Seeing failed jobs
- Retrying failed jobs
- Canceling active jobs
- Reviewing jobs that need attention
The Chat Top Bar is optional. Memory Books works without it.
Open a character chat or group chat.
Then look beside the chat input box for the magic-wand icon. This opens the SillyTavern Extensions menu.
Click the magic wand and look for Memory Books.
If Memory Books appears there, it is already installed. Continue to Part 3: Open Memory Books.
- Open SillyTavern.
- Open the Extensions panel.
- Select Install Extension.
- Paste the official Memory Books repository address.
- Install the extension.
- Reload SillyTavern if prompted.
- Open a character chat or group chat.
After the chat loads, Memory Books adds scene-selection controls to the messages. This may take several seconds.
You do not need SillyTavern Extras. Memory Books is a SillyTavern extension, not an Extras module.
Look for either of these signs:
- Memory Books appears in the magic-wand Extensions menu.
- Chat messages contain the scene buttons ► and ◄ when their message actions are expanded.
If neither appears:
- Wait up to ten seconds.
- Refresh the page.
- Return to the Extensions panel.
- Confirm that Memory Books is installed and enabled.
- Reopen the chat.
The Memory Books settings are inside the Extensions menu.
- Find the magic-wand icon near the chat input box.
- Click the magic wand.
- Click Memory Books.
This opens the main Memory Books panel.
The panel contains several sections, including:
- Current Scene
- Memory Status
- Current Lorebook Configuration
- Memory Profiles
- Profile Actions
- Extra Function Buttons
- Settings
You do not need to understand all of these yet.
For your first memory, you only need to establish:
- Where the memory will be stored
- Which AI connection will create it
- Which chat messages belong to the scene
Memory Books stores memories as entries in a SillyTavern lorebook.
A lorebook used for this purpose is called a Memory Book.
You have three storage options.
In the main Memory Books panel:
- Find Auto-create lorebook if none exists.
- Enable it.
- Leave the default Lorebook Name Template unless you have a reason to change it.
When you create your first memory, Memory Books will create a lorebook and bind it to the current chat if the chat does not already have one.
This removes the need to create and bind a lorebook manually.
This is the normal default mode.
Memory Books uses the lorebook already bound to the current character or group chat.
Under Current Lorebook Configuration, check Active Lorebook.
If a lorebook name appears, Memory Books can store memories there.
If it says None selected, either:
- Bind a lorebook to the chat through SillyTavern
- Enable Auto-create lorebook if none exists
- Use Manual Lorebook Mode
Enable Manual Lorebook Mode lets you choose a specific Memory Book for the current chat instead of using the normal chat-bound lorebook.
Use this when:
- You maintain a separate lorebook only for memories
- You want several chats to use a specific Memory Book
- You are configuring separate Memory Books for group-chat characters
- You understand how your lorebooks are organized
Most new users do not need Manual Lorebook Mode.
Manual Lorebook Mode and Auto-create lorebook cannot be enabled together.
A separate Memory Book is generally easier to manage.
It lets you:
- Keep memories separate from character definitions and world information
- Give memories their own context budget
- Reuse the Memory Book in another chat
- Manage activation through Lorebook Ordering
- Review or export memories without unrelated lorebook entries mixed in
For the easiest initial setup, enable Auto-create lorebook if none exists and let Memory Books make the separate book for you.
Scroll to Memory Profiles.
A Memory Profile tells Memory Books:
- Which API or provider to use
- Which model to use
- Which temperature to use
- Which memory prompt to send
- How memory titles should be formatted
- How the resulting lorebook entry should behave
Select:
Current SillyTavern Settings
This uses your active SillyTavern connection.
If your current model can respond normally in the chat, it is the simplest place to begin.
Do not create a custom profile until you have successfully created one memory.
Create a custom Memory Books profile later when you want to:
- Use a cheaper model for memories
- Use a more reliable model for structured JSON
- Give memory generation a different temperature
- Use a custom summary prompt
- Change memory activation behavior
- Use a different provider from the one used for roleplay
The Profile Settings box shows the selected profile’s:
- Provider
- Model
- Temperature
- Title format
If the provider or model says Not Set, fix your SillyTavern connection before continuing.
Memory Books includes working built-in prompts.
Custom prompts must preserve the required JSON response structure. Removing the JSON instructions can prevent Memory Books from reading the result.
Create a successful memory with the built-in prompt before changing it.
A scene is the range of chat messages that Memory Books will read for one memory.
For example:
- The characters arrive at a hotel.
- They question the desk clerk.
- They discover which room the suspect used.
- They decide to search the parking garage.
Those messages might form one scene and therefore one memory.
The next scene might begin when they reach the garage.
A useful scene usually contains:
- One event
- One conversation
- One investigation step
- One emotional development
- One change in location or goal
- One connected sequence of actions
Do not worry about finding the perfect literary boundary. The scene only needs to be coherent enough for the AI to summarize.
A scene containing only one or two trivial messages may not provide enough useful information.
A very large scene may:
- Cost more to process
- Take longer
- Exceed the model’s context limit
- Produce a less focused memory
- Increase the chance of invalid or cut-off JSON
For a first test, select a short but complete conversation or event.
Each chat message has message-action controls.
Depending on your SillyTavern layout, those controls may be collapsed.
- Move your pointer over a chat message.
- Find the message-actions button, usually shown as three dots or a small expandable control.
- Click it to expand the message actions.
- Look for the ► and ◄ buttons.
The buttons mean:
- ► Mark Scene Start
- ◄ Mark Scene End
- Find the first message that should be included.
- Click ► on that message.
- Find the last message that should be included.
- Click ◄ on that message.
Messages inside the selected range may receive a visual highlight. Exact colors depend on your SillyTavern theme.
Open the magic-wand menu and click Memory Books.
At the top of the panel, Current Scene should show:
- Start message
- End message
- Starting speaker
- Ending speaker
- Number of selected messages
- Estimated tokens
If the panel says No scene markers set, both scene boundaries have not been selected.
To start over:
- Open Memory Books.
- Click Clear Scene.
- Select a new start and end.
You can also click a different ► or ◄ button to change the appropriate boundary.
Once the scene and Memory Book are ready:
- Open the magic-wand Extensions menu.
- Click Memory Books.
- Confirm that Current Scene shows the intended range.
- Confirm that Active Lorebook shows a Memory Book, or that auto-creation is enabled.
- Confirm that the intended Memory Profile is selected.
- Click Create Memory.
Memory Books will compile the scene and send it to the selected model.
Depending on your settings, you may see:
- A confirmation window
- Advanced memory options
- A memory preview
- A group participant confirmation
- A token warning
- A generation-in-progress notification
- A completed job in the Chat Top Bar queue
These are not errors.
The confirmation window may let you review:
- The selected profile
- The effective memory prompt
- Previous memories included as context
- The current API and model
- Estimated token usage
For your first memory, keep the default options and continue.
If Show memory previews is enabled, Memory Books displays the generated:
- Memory title
- Memory content
- Keywords
You can edit these before saving.
Check that:
- The title is not blank
- The summary describes the selected scene
- Important names are correct
- The keywords are relevant
- The AI did not include unrelated commentary
Then approve the preview.
Memory previews are optional and disabled by default.
Without a preview, Memory Books saves a valid result automatically and shows a completion notification.
Do not assume the memory worked merely because the AI request finished. Check the result.
Open Memory Books.
The Memory Status section should now say that the chat has been processed up to a particular message.
The processed message should correspond to the end of the scene you selected.
Open the relevant lorebook in SillyTavern.
You should see a new entry containing:
- A numbered or formatted title
- The scene summary
- Activation keywords
- Memory Books metadata
The exact title depends on the selected title format.
If Show notifications is enabled, Memory Books should report that the memory was created.
Understand Hidden Messages
After creating a memory, some older chat messages may become hidden.
They were not deleted.
Memory Books can hide processed chat messages so they stop consuming the active chat-history budget. The saved memory then carries forward the important information.
Open:
Memory Books → General Settings → Token Saving (Hide/Unhide Messages)
The Auto-hide messages after adding memory setting has three choices:
- Do not auto-hide
- Auto-hide all messages up to the last memory
- Auto-hide only messages in the last memory
If disappearing messages would alarm you during the first test, choose Do not auto-hide. After verifying that memory creation works, switch to Auto-hide all messages up to the last memory to receive the main context-saving benefit.
The setting Messages to leave unhidden keeps a small number of recent messages visible around the boundary.
Automatic Memories need a starting checkpoint.
Create at least one manual memory in each chat before relying on automatic memory creation.
This tells Memory Books:
Everything through this message has already been processed.
Without that checkpoint, Memory Books does not know where automatic summarization should begin.
You can select the whole meaningful conversation for the first memory.
Do not automatically put the entire chat into one enormous scene.
Instead:
- Select a reasonable recent scene.
- Create one manual memory.
- Treat its ending message as the automatic-memory starting point.
If you later want to convert the older chat history, use the advanced catch-up workflow rather than trying to summarize thousands of messages at once.
After the first manual memory succeeds:
- Open Memory Books.
- Under Settings, click Automatic Memories.
- Enable Auto-create memory summaries.
- Set the Auto-Summary Interval.
- Set the Auto-Summary Buffer.
- Close or save the settings.
Try:
- Auto-Summary Interval: 30 messages
- Auto-Summary Buffer: 2 messages
Adjust these later based on your writing style.
The interval is the number of new messages Memory Books should collect for the next automatic memory.
A lower interval creates:
- More frequent memories
- Smaller and more focused summaries
- More AI requests
- More lorebook entries
A higher interval creates:
- Fewer AI requests
- Larger summaries
- Fewer lorebook entries
- A greater chance that unrelated events will be combined
For detailed roleplay, approximately 20–40 messages is a reasonable starting range.
For shorter or faster exchanges, you may prefer 40–60 messages.
The buffer leaves the newest messages out of the current automatic memory.
For example:
- Interval: 30
- Buffer: 2
Memory Books waits until enough messages are available, summarizes the earlier 30, and leaves the newest 2 messages for the next run.
This helps avoid summarizing a scene while it is still unfolding.
After enabling it:
- Continue chatting normally.
- Watch the Memory Status boundary.
- Wait until the interval and buffer requirements are met.
- Confirm that Memory Books creates the next memory.
- Open the Memory Book and inspect the new entry.
Do not assume automation is working until you have seen one automatic memory complete.
Recommended when you do not want to manage Memory Books manually.
Helps confirm whether an operation started, completed, or failed.
Recommended for your first several memories.
Previews let you catch:
- Incorrect names
- Missing events
- Invalid summaries
- Poor keywords
- Model misunderstandings
Once you trust the model and profile, you can disable previews for a more automatic workflow.
The divider or jump button shows how much of the chat Memory Books has processed.
This makes it easier to see where remembered history ends and unsummarized chat begins.
Enable this only after making the first manual memory in the chat.
Enable this after you understand that hidden messages are not deleted.
New users can generally ignore:
- Manual Lorebook Mode
- Custom Memory Profiles
- Custom memory prompts
- Summary Prompt Manager
- Consolidation Prompt Manager
- Context Settings
- Trackers and Side Prompt Sets
- Regex integration
- Separate group-character Memory Books
- Lorebook Ordering integration
- Compaction
- Consolidation
- Custom title formats
- Slash commands
These are useful features, but none is required to create and use ordinary memories.
Use this section when you know what information you want to preserve but do not know which tool to choose.
A Memory summarizes one selected scene.
Use it for:
- Events
- Conversations
- Decisions
- Emotional developments
- Discoveries
- Conflict and resolution
- Changes in plans or relationships
Think:
“Remember what happened in this scene.”
An Automatic Memory performs the normal memory process after enough new messages accumulate.
Use it when:
- You want regular scene memories
- You do not want to mark every scene manually
- Your chats are long and ongoing
Think:
“Keep summarizing the new chat as I go.”
A Clip saves one specific piece of selected chat text.
Use it for:
- A preference
- A promise
- A secret
- A name
- An item
- A pet
- A short relationship fact
- A line that should be preserved exactly or nearly exactly
To create one:
- Highlight text inside a chat message.
- Click the floating Clip button.
- Choose an existing Clip entry or create a new one.
- Choose whether it should always activate or activate through keywords.
- Review the result.
- Save it.
Think:
“Pin this fact.”
A Topical Clip gathers information about one subject from memories that already exist.
Use it when information about the same subject is spread across several scene memories.
Examples:
- Everything known about an NPC
- The history of a relationship
- A recurring location
- An investigation
- A character’s injuries
- A faction
- A mystery
- An important item
To create one:
- Open Memory Books.
- Click Topical Clip.
- Choose the source Memory Book.
- Enter the topic.
- Enter activation keywords, or let the topic supply them.
- Choose whether to create a new entry or update an existing Clip entry.
- Choose the generation profile.
- Generate the draft.
- Review it.
- Save it.
Think:
“Collect everything my memories say about this subject.”
A Side Prompt asks the AI to maintain an ongoing tracker.
Use it for information that changes repeatedly, such as:
- Relationship status
- Current mission
- Inventory
- Injuries
- Character statistics
- Unresolved plot threads
- NPC lists
- World state
Think:
“Keep this tracker updated.”
Consolidation combines several memories into a higher-level recap.
For example:
- Several scene memories become an Arc
- Several Arcs become a Chapter
- Several Chapters become a Book
Use it when many separate memories describe one larger period or development.
Think:
“Roll these memories up into a larger recap.”
Compaction shortens one existing Memory Books entry while preserving its important information.
Use it when:
- A Clip entry has become too long
- A Side Prompt tracker contains repetition
- A memory is useful but wordy
- An always-active entry is consuming too much context
Think:
“Trim this entry without losing its facts.”
- What happened in these messages? Use a Memory.
- Save this exact fact. Use a Clip.
- Collect saved information about this topic. Use Topical Clip.
- Keep this changing information updated. Use a Side Prompt.
- Combine several memories into a larger recap. Use Consolidation.
- Shorten one long entry. Use Compaction.
Memory Books works in group chats without a special group-mode switch.
Start with one Memory Book bound to the group chat.
- Open the group chat.
- Enable Auto-create lorebook if none exists, or bind a lorebook manually.
- Mark and create memories normally.
- Review detected participants when prompted.
Memory Books can identify which characters participated in the selected scene and attach character filters to the memory.
This helps distinguish:
- Who performed an action
- Who witnessed an event
- Who learned a secret
- Who felt or believed something
Separate group and character Memory Books are an advanced setup.
Use them only when you need:
- Private character knowledge
- Individual emotional continuity
- Different memories for different participants
- A shared omniscient group history plus personal histories
This setup generally involves:
- Manual Lorebook Mode
- One main group Memory Book
- Character-specific Memory Book assignments
- Lorebook Ordering
- Participant review
- Optional character-focused memory prompts
Begin with one group Memory Book. Add separate books only when the story requires them.
Narrator Mode is a separate advanced setup for a normal chat where one Narrator character card writes several fictional characters.
It requires:
- Manual Lorebook Mode
- One omniscient Memory Book
- One different Memory Book for each declared fictional character
- A manually maintained Active Cast selection
Narrator Mode does not detect characters by reading names in the Narrator's prose. Select the active fictional cast before each generation. STMB stores that cast on the message and later uses it to decide which character Memory Books receive copies of the scene memory.
Do not use Narrator Mode as a beginner substitute for an ordinary one-character Memory Book. Set up normal memory creation first, then follow the Narrator Mode Technical Guide.
Check:
- Did the extension finish installing?
- Is it enabled in the Extensions panel?
- Did you reload SillyTavern?
- Did you open a character or group chat?
- Did you wait several seconds after the chat loaded?
- Hover over a chat message.
- Expand its message actions using the three-dot or message-actions control.
- Look for ► and ◄.
- Wait up to ten seconds after loading the chat.
- Refresh the page if they still do not appear.
Both boundaries are required.
- Click ► on the first message.
- Click ◄ on the last message.
Then reopen Memory Books and confirm that Current Scene shows both values.
Use one of these solutions:
- Enable Auto-create lorebook if none exists
- Bind a lorebook to the chat
- Enable Manual Lorebook Mode and select a lorebook
Check:
- The selected model can follow JSON instructions
- The response was not cut off
- The maximum response length is large enough
- The built-in prompt has not been damaged
- The API and model shown in the selected profile are correct
- The provider is reachable
- A local backend is exposed through a compatible endpoint
Try a more instruction-following model before rewriting the prompt.
They were probably hidden by the token-saving settings.
Open:
Memory Books → General Settings → Token Saving (Hide/Unhide Messages)
Change Auto-hide messages after adding memory to Do not auto-hide if you want the processed messages to remain visible.
Hidden messages are not deleted.
Check:
- Did you create one manual memory in this chat first?
- Is Auto-create memory summaries enabled?
- Have enough new messages accumulated?
- Does the interval account for individual messages from both the user and AI?
- Is a buffer delaying the run?
- Is a valid Memory Book assigned?
- Is another Memory Books job still running?
- Did the automatic run get postponed or require review?
Creating a lorebook entry and sending that entry to the model are separate stages.
Check:
- Does the entry exist in the Memory Book?
- Is the Memory Book active for this chat?
- Are its activation keywords relevant?
- Is the entry constant or keyword-triggered?
- Is the lorebook context budget large enough?
- Is Delay until recursion preventing activation?
- Does a World Info inspection tool show that the entry was sent?
If the entry was sent but the model ignored it, the remaining problem is model behavior rather than memory storage.
- Open a character chat or group chat.
- Click the magic-wand Extensions menu.
- Open Memory Books.
- Enable Auto-create lorebook if none exists.
- Select Current SillyTavern Settings as the Memory Profile.
- Mark a short scene with ► and ◄.
- Open Memory Books again.
- Click Create Memory.
- Confirm that a new entry appears in the Memory Book.
- After that succeeds, enable Automatic Memories.
Do not begin by changing prompts, creating custom profiles, configuring Side Prompts, or setting up Consolidation.
The settings are inside SillyTavern’s Extensions menu.
Look beside the chat input box for the magic-wand icon.
- Click the magic wand.
- Look for Memory Books.
- Click it.
If it is not listed:
- Open the main Extensions panel.
- Confirm that Memory Books is installed.
- Confirm that it is enabled.
- Reload SillyTavern.
- Open a character or group chat.
- Check the magic-wand menu again.
- Find the first message you want included.
- Expand that message’s actions if necessary.
- Click ► Mark Scene Start.
- Find the last message you want included.
- Click ◄ Mark Scene End.
- Open Memory Books.
- Check the Current Scene section.
The selected scene includes both boundary messages and everything between them.
Check these in order:
- Scene: Are both the start and end markers set?
- Storage: Is an Active Lorebook shown, or is auto-creation enabled?
- Profile: Does the selected profile show a valid provider and model?
- Connection: Can the selected AI connection generate a normal response?
- Output: Did the model return valid, complete JSON?
- Length: Was the response cut off by a small maximum-output setting?
- Preview: Is the memory waiting for approval in a preview window?
- Queue: Does the Chat Top Bar show a failed or review-needed job?
- Notifications: Did Memory Books display a specific error?
The most common first-run problems are a missing scene boundary, no selected lorebook, or a model that did not return valid JSON.
Recommended:
- Auto-create lorebook if none exists
- Show notifications
- Show memory previews, at least during setup
- Memory boundary indicator
- Auto-create memory summaries, after the first manual memory
- Auto-hide messages, after you understand what hiding does
Leave advanced features alone until normal memory creation works:
- Manual Lorebook Mode
- Custom prompts
- Custom profiles
- Side Prompts
- Consolidation
- Compaction
- Regex
- Separate group-character Memory Books
- Lorebook Ordering
- Custom context settings
Use a Clip when the fact is visible in the current chat and you can highlight it.
Example:
“Mara is allergic to lavender.”
Highlight that sentence and save it as a Clip.
Use Topical Clip when the information is spread across memories that already exist.
Example:
Several memories mention Mara’s allergies, prior reactions, medication, and which flowers she avoids.
Use Topical Clip to create one focused entry about Mara’s allergies.
The rule is:
- Clip: Save this selected fact.
- Topical Clip: Gather saved facts about this topic.
Neither is an ongoing tracker. Use a Side Prompt when the information should be repeatedly updated.
Upload a screenshot that includes as much of the relevant SillyTavern window as possible.
Include:
- The chat input area
- The magic-wand icon or Extensions menu
- The visible Memory Books panel
- Any error message
- The message whose action buttons you are trying to use
Redact:
- API keys
- Account details
- Private chat content you do not want shared
- Private server addresses
- Personal information
Along with the screenshot, say what you were trying to accomplish.
For example:
“I am trying to mark the beginning of a scene, but I cannot find the button.”
The help assistant should then:
- Identify the visible screen.
- Explain what is currently open.
- Name the next control using its visible label.
- Give one immediate action.
- Avoid assuming that an off-screen control is present.
No.
Memory Books can use lorebook activation keywords without the Vectors extension. Memory generation includes automated keyword creation, so you do not have to manually invent keywords for every memory.
Vectors are an optional alternative or supplement, not an installation requirement.
If the Memory Book is your only active lorebook or World Info source, leave Delay until recursion disabled.
When no other entry starts the first recursion cycle, delaying the Memory Book until recursion may prevent it from activating at all.
Use delayed recursion only when you understand your lorebook activation chain and have another source capable of beginning recursion.
Start with one Memory Book for each continuing chat or story.
Narrator Mode is the main exception: it requires one omniscient Memory Book plus one unique book for every declared fictional character.
Outside Narrator Mode, use several only when you need:
- Separate private character knowledge
- Different Memory Books for different group members
- Reusable memories shared across chats
- Independent budgets or activation rules
- A deliberate Lorebook Ordering setup
One working Memory Book is better than a complicated configuration you cannot diagnose.
Yes.
Mark a scene and click Create Memory whenever you decide something should be saved.
Automatic Memories are optional. Manual creation gives you direct control over scene boundaries and timing.
No.
Memory Books may hide processed messages to reduce active context use. Hidden messages remain part of the chat and can be revealed again.
Check the token-saving settings if you do not want automatic hiding.
- Enable Automatic Memories.
- Choose a reasonable interval and buffer.
- Create several memories during normal use.
- Confirm that they activate correctly.
- Try Clips for individual facts.
- Add a Side Prompt only if you need a changing tracker.
- Use Topical Clip after enough memories contain information worth gathering.
- Consider Consolidation only after several related memories exist.
- Use Compaction only when an entry becomes too long.
Build the workflow one layer at a time.