LumiChat AI

Janitor AI Lorebook migration

Janitor AI Lorebook Export (2026): Move to SillyTavern

Export a Janitor AI Lorebook you own, map its keys and entries to SillyTavern World Info, import it safely and test activation without scraping private content.

Author: LumiChat AI TeamPublished:

12 min read

Quick answer

What this guide explains

You can migrate a Janitor AI Lorebook only when you own it, it is openly reusable or the creator gave permission. Save the visible source entries, map triggers to SillyTavern key arrays, lore text to content and behavior settings to World Info fields, then import and run an eight-turn activation test. A closed or private Lorebook is not an invitation to scrape, guess trigger words or reconstruct hidden text.

  • Start with ownership, not an extractor
  • Create a lossless source audit before conversion
  • Map Janitor entries to SillyTavern World Info

Featured companions

Three characters refresh on each visit. Cards play a promo video when available and otherwise show the character image.

Rei Kurosaki

Night strategist

Rei Kurosaki

A cool, dangerous game-maker who suits suspenseful banter, pursuit scenes, and sharp verbal chemistry.

MysteryTensionBanter
Start chat
Kaelith Amara

Desert stargazer

Kaelith Amara

A warm tent beneath desert stars creates an intimate but story-led setting for travelers and secrets.

DesertWarmStory
Start chat
Kageyama Maki

Onmyoji exorcist

Kageyama Maki

Kyoto occult mystery, protective chemistry, and supernatural rituals give every chat an immediate plot.

OnmyojiMysteryProtective
Start chat
Real LumiChat character library used to explain authorized Janitor AI Lorebook migration

Searches for Janitor AI Lorebook export, “extractor” and “to SillyTavern” hide two different tasks. The legitimate task is moving a book you own or may reuse without losing activation behavior. The illegitimate task is pulling a creator’s closed definitions or guessing hidden trigger words. This guide solves the first and refuses the second. It extends the Janitor AI Lorebook guide with a migration workflow and complements the broader SillyTavern character import guide without repeating either page.

Start with ownership, not an extractor

A visible character page does not automatically make every linked Lorebook, script or definition reusable. First identify the owner, visibility and license. Use Janitor AI’s current export or copy controls when they are available for your own content; interface labels can change, so do not promise a universal download button. If the book is closed, private or deliberately hidden, stop. Trigger guessing, prompt extraction and browser scripts that bypass creator controls are not a migration workflow.

Source stateMay you migrate it?Correct action
Your own LorebookYesExport or copy visible entries, then verify every field
Open/public Lorebook with reuse permissionYes, within its licenseKeep attribution and license notes
Creator sent you a file or explicit permissionYes, within that permissionPreserve the original and migration record
Closed/private LorebookNoAsk the creator; do not guess triggers or extract hidden text
Public character with hidden LorebookNo automatic rightMigrate only the fields the creator made reusable

Create a lossless source audit before conversion

Preserve the source before editing. A screenshot is not enough because it loses arrays, disabled state and activation controls. Save structured data when the platform exposes it; otherwise make a controlled table from the visible fields you are authorized to copy. Keep primary keys separate from secondary conditions, and distinguish a constant entry from a keyword entry. Count everything before and after conversion so silent loss is measurable rather than discovered halfway through a story.

  1. Save an untouched source copy and record the date.
  2. Count entries and note whether each is enabled or constant.
  3. Copy primary keys, secondary keys and content separately.
  4. Record order, position, probability, depth and recursion behavior when visible.
  5. Mark scripts or platform-only syntax for manual review.
  6. Remove secrets, personal identifiers and content you cannot lawfully reuse.

Map Janitor entries to SillyTavern World Info

SillyTavern calls Lorebooks “World Info.” Its official documentation describes entries as dynamically inserted prompt material activated by keys, with separate character, persona, chat and global scopes. Map by behavior instead of copying numeric values blindly. A Janitor label belongs in a human-readable comment, not necessarily in prompt content. Injection position, recursion, probability and selective matching differ enough that every advanced entry needs manual review.

Janitor conceptSillyTavern World Info fieldMigration check
Entry name or labelcommentHuman-readable editor label; not prompt content
Trigger wordskeyArray of primary activation keys
Additional conditionskeysecondaryReview selective matching rather than flattening
Lore textcontentMust be complete enough to stand alone when activated
Always activeconstantUse sparingly because it always spends context
PriorityorderPreserve relative order, then test collisions
Injection locationposition / depthMap by behavior, not only by numeric value
Enabled statedisableInverted Boolean: disabled means disable=true
Chanceprobability / useProbabilityVerify 100% entries before adding randomness

Build a minimal valid World Info JSON

Start with one non-sensitive entry and a small JSON file, not a bulk conversion. The example below demonstrates common SillyTavern World Info fields without containing real creator text. Keep each content block standalone because key names and editor labels are not inserted into the model context. Validate JSON syntax, use unique integer IDs and preserve unknown extension data when a trusted exporter includes it. Do not paste executable Janitor scripts into lore text and assume they will run.

{
  "entries": {
    "0": {
      "uid": 0,
      "key": ["Aster Harbor", "harbor council"],
      "keysecondary": [],
      "comment": "Aster Harbor",
      "content": "Aster Harbor is governed by a five-seat council.",
      "constant": false,
      "order": 100,
      "position": 0,
      "disable": false,
      "probability": 100,
      "useProbability": false,
      "depth": 4
    }
  }
}

Import and bind the Lorebook to the right scope

Import the JSON through the current SillyTavern World Info interface, then open the editor before binding it. Confirm entry count, Unicode text, keys, enabled state, probability and order. Bind it to the narrowest scope that needs it. Character Lore follows one character across chats; Chat Lore stays in one branch; Persona Lore follows the active persona. Only the primary character Lorebook is embedded when exporting a character card, so keep standalone backups too.

BindingScopeUse it when
Character LoreEvery chat with one characterThe facts belong to that character or world
Chat LorebookOne conversation onlyThe facts are specific to a branch or campaign
Persona LorebookEvery chat using one personaThe facts describe the user role or persona
Global World InfoAny selected chatThe book is intentionally reusable across characters

Run an eight-turn activation regression test

A successful import is not proof of behavioral parity. Run the eight turns below with a disposable chat and inspect the final prompt or World Info activation display when available. Test absent keys as carefully as present keys: an entry that fires everywhere is just permanent context. If an entry never fires, check key spelling, scan depth, case and whole-word settings before rewriting the content. If too many entries fire, reduce broad keys and check recursive activation.

TurnTestPass condition
1Mention no keysNon-constant entries stay absent
2Mention one exact primary keyOnly its intended entry activates
3Use different letter caseBehavior matches the configured case rule
4Use a partial wordWhole-word behavior matches the setting
5Trigger two related entriesOrder and budget produce coherent context
6Mention a secondary conditionSelective logic matches the original intent
7Change scene and mention the key againEntry still activates without duplicating prose
8Reopen the chatCharacter or chat binding remains attached

When manual migration—or hosted chat—is simpler

Manual migration is best for a valuable, authorized book whose behavior you intend to maintain. Rebuilding a small world can be faster than repairing an opaque converter, especially when platform-only scripts or positions are involved. The Chub AI character card guide explains another portable-card workflow. If your real goal is simply to choose a hosted role and continue chatting rather than maintain files and trigger logic, compare the LumiChat character library. LumiChat is separate and cannot unlock Janitor AI content.

FAQ

Can I export a Janitor AI Lorebook?

You can export or copy your own content and openly reusable or authorized content using the current controls available to you.

Can I download a private Janitor AI Lorebook?

No. Ask the creator for a file or permission; do not scrape, guess triggers or reconstruct hidden entries.

Can SillyTavern import a Janitor AI Lorebook directly?

Formats and platform features differ. Treat it as a field-mapping conversion and verify the imported World Info entry by entry.

What happens to Lorebook keys?

Primary triggers map to key arrays. Secondary conditions need selective-logic review rather than being merged into one text string.

Where should I bind the converted book?

Use Character Lore for one character, Chat Lore for one branch, Persona Lore for one user role or Global World Info for intentional reuse.

Why did my imported Lorebook not activate?

Check enabled state, exact keys, scan depth, case sensitivity, whole-word matching, budget and binding.

Can Janitor AI scripts run as SillyTavern lore text?

Not automatically. Script logic and lore content are different; review or rebuild supported behavior instead of pasting executable code.

Can LumiChat import the private Lorebook for me?

No. LumiChat is a separate hosted character platform and does not bypass another creator’s permissions.

Kageyama Maki

Continue in LumiChat

Turn this guide into a real conversation

Browse active characters, choose a personality that fits, and start chatting in seconds.

Enter chat