Local RAG and Lorebooks

Local RAG is Abolitus's memory-retrieval layer for lorebooks.

In plain terms, it helps the app re-surface the right world facts at the right time instead of forcing you to keep every important detail in the live chat window.

Why Lorebooks Matter

Long roleplay sessions fail when the model has to juggle too many facts at once.

Lorebooks let you move durable facts out of ordinary chat and into entries that can be injected when relevant.

Use lorebooks for:

World rules.
Factions, places, and recurring objects.
Relationship facts.
Character secrets.
Setting terminology.
Rules that should survive across many scenes.

What "Local" Means Here

The retrieval layer runs on your device. The memory process does not need your lorebook text to pass through an Abolitus server just to decide what is relevant.

That is the key privacy promise of this feature.

Lorebook Scopes

Abolitus supports several scopes so you can control how broadly an entry applies.

Global

Use this for facts that should be available across your wider workspace.

Character Default

Use this for facts that belong to a specific character or the stories usually attached to that character.

Session

Use this for temporary scene facts that are relevant to the current working session rather than your long-term library.

Triggering Basics

Lorebooks can activate based on keys and related matching rules.

This makes them useful for more than just static insertion.

Typical uses:

Mention a place name and retrieve the place description.
Mention a faction and retrieve its internal rules.
Mention a nickname and retrieve a hidden relationship note.

Secondary Keys and Selective Logic

Abolitus supports more than simple one-word matching.

You can combine primary keys with secondary conditions to control when an entry should fire more narrowly.

This is useful when an entry should appear only:

In one context but not another.
When two concepts appear together.
When one qualifier is present or absent.

If you are importing from another advanced roleplay tool, this is one of the places where Abolitus can preserve a more nuanced memory setup.

Entry Placement

Lorebook content can be inserted at different points around the character and the near-turn guidance.

Why this matters:

Facts placed earlier help frame the whole scene.
Facts placed closer to the current turn can influence the next reply more strongly.

You do not need to micromanage this on day one, but it becomes valuable when you are tuning complicated story setups.

Constant, Sticky, Cooldown, and Delay

These controls exist because not every memory should behave the same way.

Constant

Use constant entries for rules that should always be eligible rather than waiting for a trigger.

Sticky

Use sticky entries when you want a matched memory to keep influencing the scene instead of appearing once and disappearing immediately.

Cooldown

Use cooldown to stop a frequently matched entry from firing too often.

Delay

Use delay when an entry should not become active immediately at the start of a scene.

Groups and Selection Strategy

Entries can also be grouped.

This helps when several entries are related and you do not want them all to flood the prompt at once.

Two common patterns are available:

Priority-based selection when one entry should reliably win.
Weighted random selection when you want controlled variation.