Keep track of who's in the room in SillyTavern
On this page
If a SillyTavern character forgets who is in the room, first check whether the relevant facts still reach the model. Then try a short current-scene note that records who is present and what each character knows.
The note gives you current facts to inspect and update. It needs to change with the scene, and the model can still get a fact wrong. The steps below follow SillyTavern's documentation; they have not been tested here with a particular model.
Check whether the model received the fact
A fact can remain visible in your chat while falling outside the active context. SillyTavern's Common Settings documentation explains that messages above the dotted context line are not sent to the model.
After a reply gets a detail wrong, open Prompt Itemization. Check whether the request included the departure, clothing change or discovery that established the current state. Also look for a character description, summary or old note that contradicts it.
This separates two problems. If the fact was absent, putting a concise version into the request is a useful next test. If the fact was already present and unambiguous, the model may still have failed to follow it. Adding the same sentence repeatedly does not prove that problem is solved.
Keep prompt inspection local. A full request can expose private conversation text.
Give current state its own short note
A character card describes a character across scenes. A current-state note records what is true at this moment. Someone's usual coat belongs in their description; where they left it during this scene belongs in the state note.
Here is an invented scene example you can adapt. It is not a model-generated reply or an observed test result:
Current scene: archive reading room, shortly after sunset.
Present: Mara and Ivo.
Elsewhere: Lena is waiting outside the closed door.
Clothing: Mara's blue coat hangs on the chair; she is not wearing it.
Object: the brass key is in Ivo's left pocket.
Knowledge: Ivo found the hidden letter. Mara has not seen it or
been told about it. Lena heard voices but not the conversation.
Open action: Mara asked what Ivo found. Ivo has not answered yet.
Keep only facts that matter to the next exchange. A note that repeats every event in the story becomes another long history to maintain.
Use names where a pronoun could point to two people. If the story has not established a fact, leave it unknown rather than filling the gap with a guess.
Separate what happened from who knows it
Your prompt may include a secret that only one character knows. Record that boundary explicitly, alongside who is physically present.
In the example, Ivo found the letter. Mara is in the same room now, but that alone does not establish that she saw the discovery. Lena is outside; hearing voices does not give her the contents of a private exchange.
If this distinction keeps breaking, add a plain instruction beside the scene facts. For example:
Keep each character's knowledge limited to what they witnessed or were told. When a fact is unknown to them, let them ask or react to what they can observe.
This is an example instruction, not a guarantee of compliance. Test it on the next exchange that depends on the secret. General questions about the setting will not tell you whether the model respects that boundary.
Try the chat-specific Author's Note
SillyTavern's Author's Note can insert temporary information into a prompt. Its documentation specifically gives current locations and physical conditions as possible uses.
For a small insertion test:
- Save your existing note and settings so you can restore them.
- Open Author's Note from the options beside the chat input. Put the scene snapshot in the chat-specific note rather than the default for new chats.
- Choose In-chat at depth 0, which the documentation places at the end of chat history. Set insertion frequency to 1 for every user input. Frequency 0 disables insertion.
- Generate an ordinary turn and inspect the assembled prompt. Confirm that the snapshot appeared and describes the scene correctly.
These are documented controls, not a claim that we tested your installed client or found the best position for every model. If you change placement later, check the assembled request again.
The chat-specific note does not automatically transfer to a new chat. That is useful for keeping temporary facts out of unrelated scenes, but it also means a fresh-chat test needs its own note.
Update the snapshot when the scene changes
When Lena enters, update who is present. When Mara reads the letter, update her knowledge. When the key changes hands, replace its old location rather than leaving both versions in the note.
Review the snapshot at a scene transition, time skip or branch. If you regenerate an earlier turn or resume an alternate path, restore the facts for that point. A note describing a later event can accidentally give the model future information.
If you use an automatic tracker or summary, inspect its changes instead of assuming they are correct. A mistaken fact in a repeatedly inserted note can keep returning in later replies.
The extra note also becomes input when included. Updating it can affect prompt-cache reuse, depending on its placement and your provider. Keep it short, but do not preserve an outdated fact merely to avoid changing the prompt.
Test continuity with the scene you care about
Choose one detail that recently failed. Ask for the next natural exchange in a scene where that detail matters, then check the reply against the snapshot. If it still fails, keep the prompt available for your own comparison and change one instruction at a time.
Check whether the reply keeps absent characters offstage, respects an undisclosed fact, or places the coat correctly. Pick the check relevant to your problem rather than trying to evaluate everything at once.
Also inspect the accepted history. If an earlier reply put Lena in the room and you continued from it, the new prompt now contains that version too. Correct the mistaken turn or test from a clean point before adding more reminders.
If you want to try Arscelare with your own character, the SillyTavern connection guide covers setup. Keep the same scene snapshot when comparing models, then judge each reply against the facts. A successful exchange is a useful observation, not proof of reliable memory across a long chat.