Use the Lorebook for Backstory

The Lorebook holds backstory entries that stay out of the conversation until they are relevant. A long biography sent on every message costs tokens, slows replies, and dilutes what she is actually answering. A Lorebook entry waits for its word.

Understand the trade

• Every entry has a title, trigger keywords, and lore content.
• When one of the keywords appears in your message, the entry is added to that turn.
• An entry with no keywords is injected into every turn. The app marks it as always on, and it counts against the token budget on every message.
• Priority orders entries against each other when several match at once.
• The toggle on the left of each row turns an entry on or off without deleting it.

Add a backstory entry

Goal

Give her a piece of world knowledge she brings up only when it matters.

Before you start

Decide what the entry is for, and write down the handful of words you would use when you want her to remember it. Those become the keywords.

Steps

1. Open Settings → Lorebook.
2. Confirm the header names the character you expect. The Lorebook belongs to the active character.
3. Select Add entry.
4. Expand the new row and fill in:
   • Title: a short name you will recognise later, such as Her apartment.
   • Trigger keywords: comma-separated words, for example apartment, flat, home, bedroom.
   • Lore content: the facts themselves, written the way you would explain them to a person.
   • Priority where the form offers it.
5. Leave the toggle on.
6. Return to the chat and send a message containing one of the keywords.
7. Confirm that her reply uses the detail.

Expected result

She answers with the stored detail on messages that mention a keyword, and ignores it otherwise.

If something goes wrong

• If the entry never arrives, check the spelling of the keywords against the words you actually type. Matching is literal, so apartment does not match apartments.
• If she brings it up too often, the keywords are too broad. Narrow a generic word like home to something more specific.
• If several entries compete and one keeps winning, use priority to settle it.
• If every reply feels heavier and slower, look for an entry with no keywords. An always-on entry is the usual cause.

Make an entry always on

Leave the keywords field empty. The row is then labelled always on.

Use this sparingly. It is the right choice for one or two facts that shape every single reply, such as her name for you or a hard rule about her character. It is the wrong choice for a paragraph of setting detail.

If something goes wrong

If replies got noticeably slower after adding an always-on entry, turn its toggle off and give it keywords instead.

Know what the Lorebook is not

• It is not memory. It does not learn anything, and it does not change as you talk.
• It is not the persona or the personality sliders. Those live under Settings → Characters.
• It is not training. Nothing you write here is sent anywhere or used to train any model. It is a local entry in your own database, and it is included in a full backup.

---