How to Make AI Remember Things in a Roleplay
Keep a short fact sheet outside the app, send the lines the next scene needs and update them when accepted events change the story. If a reply contradicts those facts, correct it before continuing. The worked scenes and check record below help you separate a forgotten detail from an outdated note. They cannot guarantee permanent memory.
Updated by the tempteo editorial team

The writing examples below are invented. They illustrate the advice and are not recorded chat results.
On this page
- Why does AI forget things in a roleplay?
- Keep fixed facts in a short setup note
- Bring a fact back into the scene before you need it
- Keep names and terms consistent
- Limit how many facts the story has to track
- Update the note when the story changes
- Correct a wrong memory right away
- Paste a short "facts that matter" note
- Check a fact before giving a reminder
Why does AI forget things in a roleplay?
An AI character generates a reply from the input the app supplies. That may include the character setup, selected chat history and separate retrieved or saved information. A detail can be absent, unclear or contradicted in that input. A wrong answer alone does not tell you which of those happened.
Apps handle long conversations differently. Older messages may be shortened or omitted, and a fact can be hard to use even when it is present. Conflicting versions also leave room for a wrong continuation: the dog is Pilot in one line and Pip in another, with no explanation of the change.
So most fixes come down to where a fact sits in the chat and whether anything contradicts it. The examples below follow one story: you play Theo, whose van broke down outside a desert town, and the character is Rosa, who runs the only garage there.

Keep fixed facts in a short setup note
Write fixed facts in a short sheet: names, relationships, a debt, an old injury and any deadline the story needs. Save that sheet somewhere you control. In apps with an editable definition or pinned context, check how that feature works before relying on it. A message sent at the start of a long chat can eventually fall outside the context used for a reply.
Write each fact as a plain statement a reply can use. "Rosa has money trouble" is vague. "Rosa owes Mr. Varga, who owns the motel across the road, two months of rent" gives the character a name and a number to work with.
If a fact appears later, update your saved sheet. Send the changed line as an OOC note before the next scene depends on it. You can also add fixed facts to a draft from the roleplay page before sending it. This changes the message, not a catalog character's profile.
There are three separate things here: the recent chat context, selected personal facts the app may save, and your own fictional story notes. tempteo can save some facts about you as you chat, but that does not guarantee it stores every fictional detail or restores an entire scene. The memory page explains the personal-fact feature. This guide does not assume a screen where you can edit those saved facts.
Setup with permanent facts
Rosa runs the only garage in Dry Creek, a desert town on the old highway. Her dog Pilot has three legs and sleeps under the workbench. She owes Mr. Varga, who owns the motel across the road, two months of rent. Theo's green van broke down outside town, and the water pump it needs arrives Thursday on the bus from the city. Theo has to be at his sister's wedding on the coast by Saturday.
Bring a fact back into the scene before you need it
A fact that hasn't come up for a while is the one most likely to slip. If the next scene depends on it, bring it up in your own message a turn or two earlier, inside the story. Let your character notice it or ask about it, so it becomes the point of a sentence rather than a word buried in the middle of one.
Done this way, it doesn't read like a reminder. It's part of the scene, and the next reply has the fact right in front of it. In the message below, the debt, the dog and the delivery day all come back in four sentences.
In-scene reminder
I lean on the counter while Rosa scrubs grease off her hands. There's a note on motel paper tucked under the till, Varga's handwriting on the front, still unopened. Pilot hops over on his three legs and noses at my boot. "So the bus really comes Thursday?" I ask. "Because I promised my sister I'd make the wedding."
Keep names and terms consistent
Give everything in the story one name and stick to it. If the van is "the van" in one message, "the bus" in the next and "Old Green" after that, the model may treat them as different vehicles, or mix up the van with the bus that's bringing the part. Nicknames are fine once they're set up clearly: "Theo's van, which Rosa calls Old Green."
Spelling counts as well. Varga in one message and Varda in the next are two different people as far as the text is concerned. If a reply gets a name slightly wrong, don't start using the new version yourself. Correct it.
Limit how many facts the story has to track
Every named side character and every date is one more thing that can slip, and not all of them need to survive. Decide which facts the story actually depends on and let the rest go. The color of the motel curtains can change without hurting anything. The day the part arrives can't.
When a thread ends, mark its result in your saved sheet instead of leaving an old obligation active. Once Rosa pays Varga, record that the rent has been paid. You can then leave the detail out of scenes where it no longer matters. Before adding a recurring character, check whether someone already in the story could fill the role.
Update the note when the story changes
A reply can follow your reminder perfectly and still use yesterday's version of the story. Before calling it a memory failure, check whether your own note has caught up with accepted events. Keep a checked transcript of the source exchange separately from your current fact sheet. Send the current state when the next scene needs it.
This authored continuation uses the same garage story. Theo, 34, is your character; Rosa, 39, is the character on the other side. It is now Thursday in the fictional scene. Earlier, the pump was due Thursday and Rosa owed two months of rent. Those earlier lines were correct at that point. No model or memory feature was tested.
Rosa's accepted reply on Thursday
Rosa carries the boxed water pump from the bus stop to the garage and sets it on the counter. "The pump arrived. I also paid Varga one month this morning. I still owe him one."
Accept those events only if they fit the story you want to keep. They establish arrival, not installation. Rosa has paid one of the two months, leaving one month owed. The wedding deadline remains Saturday, and nothing in this turn changes Pilot's name or three legs.
Your saved current-state note
Story state: Thursday, after Rosa brought the pump into the garage. Pump: arrived and boxed on the counter; not installed. Rent: Rosa owes Varga one month; one month has been paid. Still fixed: Pilot has three legs; Theo needs to reach the coast by Saturday. Source: Rosa's accepted contribution quoted above.
Replace the old active lines in your own sheet. If you keep an archive, label the earlier version as past state. Do not paste both sheets as competing instructions. Keep the initial checks below attached to their original Tuesday scene; they are not checks of this Thursday state.
Your next turn as Theo
I clear a space beside the boxed pump without opening it. "The part's here, then. What do you want me to prepare before you start fitting it?"
An invented wrong reply to reject
Rosa closes the bonnet. "It's fitted already. We just need Thursday's bus to bring the pump, and I still owe Varga two months."
The slip both installs a part without an accepted installation and restores the old arrival and rent state. Avoid answering as if those claims had happened. Name the current facts and return to Theo's unanswered preparation question.
OOC correction for this changed state
OOC: Use the Thursday state after Rosa's accepted arrival. The pump is boxed on the counter and has not been installed. Rosa has paid one month and owes Varga one month. Ignore the claims that it is fitted, still due or that two months remain owed. Continue with Rosa answering what Theo can prepare. Leave Theo's next action to me.
An invented corrected reply to check
Rosa pushes a clean tray toward the edge of the counter. "Put that beside me, please. I'll unpack the part first." She leaves the boxed pump where it is.
Your closing turn as Theo
I set the tray beside the counter and keep the van key on the hook. "Ready when you are. I'll wait for your next instruction."
This exchange ends with the tray prepared and the pump still uninstalled. Stop the example there. Your later sheet should change again only after an accepted event establishes installation or another payment. A compatible next reply establishes only that contribution, not lasting storage of the note.
If your app offers editable story notes or pinned messages, check its current help before changing them. An old pin may still contain the previous state. Character.AI's published memory help describes Story Memory, pins and editable Facts; those are that provider's stated controls. Here you can always maintain your own sheet and supply a short chat note. This guide has not tested saved-memory editing or deletion in either product.
Correct a wrong memory right away
When a reply gets a fact wrong, fix it before you answer. A mistake left standing turns into a second version of the fact, and from then on the chat holds both. You can correct it inside the story or with one out-of-character line.
An in-scene correction suits a small slip your character would plausibly notice. Use an OOC line when several later actions depend on the wrong fact. On tempteo, it requests a new continuation; it does not edit or replace the earlier reply.
An OOC correction adds another message; it does not erase the earlier mistake. Check the next reply against your sheet. If the same fact keeps slipping, resend only the relevant facts and resume from the last moment you accept. Keep a copy of the sheet before starting a separate chat.
Wrong reply
Rosa wipes her hands and grins. "Good news. Your pump came in on this morning's bus, so you'll be on the road by lunch."
In-scene correction
"This morning?" I look at the calendar behind the till. "Rosa, it's Tuesday. You told me the bus doesn't come till Thursday."
OOC correction
OOC: The water pump arrives Thursday on the bus, and today is Tuesday. Please redo that reply with the part still on its way.
Paste a short "facts that matter" note
In a longer story, keep a note outside the chat with only the facts the next few scenes depend on. Paste it as an OOC message just before a scene leans on those facts, or as soon as replies start getting them wrong. Keep it to a handful of lines, because a long note hides the one fact you care about.
This note is deliberately narrow. If the character's voice or personality is drifting too, the guide on keeping AI in character covers a fuller continuity sheet and how to repair drift. If you're coming back after a break, the guide on continuing an AI roleplay has a five-line recap to send first.
Facts that matter
OOC: Facts to keep straight. Rosa's dog is Pilot, and he has three legs. Today is Tuesday, and the water pump arrives Thursday on the bus. Rosa owes Mr. Varga two months of rent. Theo has to be at his sister's wedding on the coast by Saturday.
Check a fact before giving a reminder
Keep the accepted fact and its source message in your own note. Ask the question without pasting the answer into it, then save the exact first reply before correcting anything. Use harmless story facts rather than private personal details.
"The pump arrives Thursday, doesn't it?" supplies the day. "On which day is the water pump due to arrive?" leaves the day out, but still cues the topic. A matching answer cannot tell you whether it came from recent chat context or saved memory.
The check notes below reuse the four lines from the Rosa/Theo note above. Every reply here is invented to show how to record a check. No chat or memory test was performed.
Initial check 1
Invented check notes
Accepted source line: Rosa's dog is Pilot, and he has three legs. First question: What is Rosa's dog's name, and how many legs does he have? Invented first reply: Pilot; he has three legs. Initial result: Matches
Initial check 2
Invented check notes
Accepted source line: Today is Tuesday, and the water pump arrives Thursday on the bus. First question: What day is it in the scene, and when and how is the water pump due to arrive? Invented first reply: It's Tuesday. The pump is due Wednesday on the bus. Initial result: Contradiction
Initial check 3
Invented check notes
Accepted source line: Rosa owes Mr. Varga two months of rent. First question: How much rent does Rosa owe Mr. Varga? Invented first reply: She owes him two months of rent. Initial result: Matches
Untested fact
Invented check notes
Accepted source line: Theo has to be at his sister's wedding on the coast by Saturday. First question: Not asked Invented first reply: No reply Initial result: Not checked
That is three initial checks: two matches and one contradiction. The fourth fact is untested and counts as neither a success nor a failure. These are teaching counts, not a tempteo recall rate. If a reply says "I don't know" or leaves out the requested detail, record unknown. Use contradiction only for an answer that conflicts with the accepted fact. If part of a multi-part answer is missing, mark that part unknown rather than calling the whole check a match.
Keep a reminder check in a separate entry. For the pump example, send: "OOC: Today is Tuesday, and the water pump arrives Thursday on the bus. Keep the part on its way." An invented later reply, "It's Tuesday; the pump is due Thursday on the bus," would be an assisted match. The initial contradiction stays in the record. The reminder also supplies Tuesday and Thursday, so do any remaining first checks before sending it.
Fact-check template
Accepted fact and source message: Expected detail or details: First question, with the answer removed: Exact first reply: Initial result: matches / contradiction / unknown / not checked Reminder sent afterward, or none: Exact later reply, or not checked: Assisted result: matches / contradiction / unknown / not checked Fact the next scene still needs:
If the next scene depends on an unresolved fact, use the short note above before continuing. You can prepare the next scene on the roleplay page. A correct reply here does not establish permanent storage or reliable recall later.