Night strategist
Rei Kurosaki
A cool, dangerous game-maker who suits suspenseful banter, pursuit scenes, and sharp verbal chemistry.
Chat memory guide
Learn how Janitor AI Chat Memory works, write a compact memory summary, use a reusable prompt and fix forgetting without overloading context.
12 min read
Quick answer
Use Janitor AI Chat Memory as a compact, editable briefing for one conversation—not as a transcript. Record the relationship, current setting, confirmed facts, unresolved goals and the latest meaningful change; remove decorative dialogue and stale events. Update it after a real plot shift, then run a direct recall and contradiction test. Put permanent identity in Persona, conditional world facts in a Lorebook and recent wording in normal chat history.
Featured companions
Three characters refresh on each visit. Cards play a promo video when available and otherwise show the character image.
Night strategist
A cool, dangerous game-maker who suits suspenseful banter, pursuit scenes, and sharp verbal chemistry.
Nocturnal hunter
Playful hunter-and-rival energy for users who prefer suspense, reversals, and a partner who pushes back.
Ginza club queen
An elegant Tokyo Ginza club character with warm, ritual-rich replies for users who want refined emotional companionship.

Chat Memory setup, templates and fixes
Janitor AI Chat Memory is most useful when a long conversation starts losing the facts that still matter. It is not a promise that the bot remembers every message forever. Treat it as a short editor-approved briefing that competes with the character definition, Persona, recent messages, Lorebook entries and the reply itself for limited context.
We reviewed the current JanitorAI entry points and Help Center guidance on August 9, 2026, then separated the memory jobs that users often mix together. Menus, model routes and token behavior can change, so verify the live chat tools before following an old screenshot. The method below remains useful because it is based on information priority, not one button label.
| Layer | Best use | Keep it concise because | Common mistake |
|---|---|---|---|
| Character definition | Stable identity, voice and core behavior | It is loaded repeatedly | Writing an entire novel as permanent identity |
| Persona | Your stable name, role and relationship baseline | Every extra detail takes context | Storing temporary scene events here |
| Chat Memory | Current relationship state, major events and open goals | It should summarize, not duplicate history | Pasting the full transcript |
| Recent chat | Exact wording, emotion and immediate actions | Older turns eventually lose influence | Expecting turn one to remain equally visible forever |
| Lorebook | Conditional places, factions, objects and world facts | Entries should activate only when relevant | Using it as a diary of every conversation |
| Advanced prompt | Style, pacing and response rules | Conflicting instructions create drift | Repeating facts that belong in memory |
The main rule is simple: store each fact in the smallest layer that needs it. Repeating the same fact in Persona, Chat Memory, Lorebook and an advanced prompt wastes space and can create contradictory versions.
A useful memory answers five questions in a few lines: Who are the participants? What relationship has been established? Where and when is the current scene? Which facts have been confirmed? What unresolved decision should affect the next reply?
Keep state, not prose. “Mara learned that Eli hid the train ticket and now distrusts him” is more useful than six paragraphs recreating the argument. Include a correction when it changes canon, such as “The meeting is Friday, not Thursday.” Remove greetings, repeated compliments, decorative description and events that no longer affect the story.
Do not use private identifiers as test facts. A fictional color, promise, destination or nickname is enough to measure recall.
Use this as a structure, then replace every bracketed item. Shorter is usually better than filling every field.
This format is intentionally factual. It gives the model a current state without forcing one exact line of dialogue or rewriting the character’s permanent personality.
If the current chat can still see the important scene, ask for a draft rather than trusting an automatic summary blindly:
Summarize the conversation as compact memory notes. Keep only established relationship facts, current setting, promises, boundaries, unresolved goals, important corrections and the latest emotional change. Remove greetings, repeated dialogue, decorative prose and speculation. Use short factual bullets and do not invent missing details.
Read the result before saving it. Delete invented motives, fix names and dates, and shorten repeated facts. A fluent summary can still be wrong; Chat Memory should contain verified canon, not the model’s most confident guess.
Chat Memory describes what has happened in this specific conversation. A Lorebook describes world knowledge that becomes relevant when a key appears: a city, faction, artifact, family rule or historical event. One changes as the relationship progresses; the other can be reused across scenes and characters.
If one plot fact must always remain visible in the current chat, keep it in Chat Memory. If a detailed world fact matters only when “Elderglen” or another precise key is mentioned, keep it in a Lorebook. The separate JanitorAI Lorebook guide covers keys, compact entries, imports and activation testing without turning the worldbook into a transcript.
| Symptom | Likely cause | First fix |
|---|---|---|
| Old facts disappear | Context pressure pushes older history out | Refresh a compact summary of only active facts |
| Bot repeats the summary | Memory is written as dialogue or commands | Rewrite it as neutral state notes |
| New facts are ignored | Memory contains stale or conflicting canon | Replace obsolete lines and remove duplicates |
| Character voice changes | Summary overwrites personality or style | Move identity back to character definition |
| Lore appears in every scene | Lorebook keys are too broad | Use distinctive keys and shorter entries |
| Replies become generic | Permanent prompts and memory are bloated | Audit every always-loaded layer |
The model route also matters. Different models can interpret the same character and memory differently. Record the active route during testing and do not assume a summary that worked on one model will behave identically after a change. For outages, login loops and blank replies, use the separate Janitor AI not working guide; those failures are not automatically memory failures.
Use one safe fictional scene. In turns 1–5, establish a nickname, destination, promise and boundary. In turns 6–10, change location and correct one harmless detail. Update Chat Memory once. In turns 11–15, discuss an unrelated topic. In turns 16–20, return to the promise and ask the character to choose an action.
Score five things: correct recall, respect for the boundary, acceptance of the correction, preservation of character voice and recovery after one contradictory message. Run the same script twice—once with a concise memory and once without it. This produces better evidence than asking “Do you remember?” because a model can answer yes without retrieving the right fact.
Do not paste passwords, financial records, legal identifiers, private workplace information, medical records or intimate material you cannot tolerate being retained. Use fictional details for testing and review the current platform’s storage and deletion controls.
Also avoid instructions that attempt to bypass laws, age rules or platform safeguards. Chat Memory is a continuity tool, not a safety override. Keep characters clearly adult when using adult-oriented roleplay and separate fictional canon from real personal data.
Start a fresh chat when the current memory contains too many mutually exclusive timelines, the character definition has changed substantially, or you can no longer explain which facts are canon. Save a short transition note you are allowed to keep, then rebuild only the current relationship and goal.
If you are comparing products rather than repairing one chat, use the AI companion long-term memory guide and the Character.AI vs JanitorAI comparison to separate productized memory controls from manual context management.
Write Chat Memory like a compact production brief: stable relationship, current state, confirmed facts, meaningful correction and next goal. Keep Persona for identity, Lorebook for conditional world knowledge and recent chat for exact wording. Update after plot changes, not on a timer, and prove the result with a recall plus contradiction test.
You can run the same 20-message benchmark with LumiChat characters or start from LumiChat Discover. The three random real-character cards below refresh on each visit so the test is not limited to one personality.
It is an editable summary layer for important facts and current state in one conversation. It is more useful as compact notes than as a complete transcript.
Use the shortest summary that preserves active canon. Prioritize a few confirmed facts and remove prose, repetition and obsolete events.
Update after a meaningful reveal, correction, boundary change, scene transition or new goal. Do not append after every message.
No. Chat Memory tracks one conversation; a Lorebook supplies conditional world facts when relevant keys appear.
The summary may be too long, contradictory, stale or competing with large permanent prompts. The selected model route can also change behavior.
Yes, but review every draft. Models can omit corrections or invent motives, so save only facts you have verified.
No. It improves continuity by placing selected facts into context, but model limits, configuration and changing product behavior still apply.
LumiChat AI Team
Editorial Team
LumiChat AI 产品与编辑团队,负责核验产品现状、角色路径与可复用操作方法。
Continue the conversation naturally
Status and troubleshooting
A symptom-first Janitor AI troubleshooting guide: identify the failing layer, apply the smallest fix and avoid unsafe “unblocked” shortcuts.
Replika subscription guide
Replika pricing is a four-level decision rather than one subscription: Free tests the basic companion, Pro adds relationship and voice tools, Ultra adds deeper conversation and saved memory, and Platinum adds advanced video and training features.
World memory guide
A lorebook is conditional world knowledge, not unlimited long-term memory. Good entries inject one relevant fact when a precise key appears; bad entries fire constantly or never fire.
Hands-on AI companion comparison
Guided Story Memory and native voice meet a configurable JLLM and proxy workflow. Compare recall, control, setup, and the real work behind a long roleplay.