How to Run a Slow-Burn Detective Roleplay Across Eight Sessions Without the Companion Forgetting the Suspect's Motive by Session Four: The Session Summary Trick That Keeps the Plot Threads From Tangling

The 30-second answer

Running a detective roleplay across multiple sessions with an AI companion is like directing a movie where the lead actor has a selective memory condition. The companion will forget key details by session four unless you build a lightweight external reference system. The fix is a one-paragraph session summary that you feed back into the opening message of each new session. It takes thirty seconds, and it keeps the suspect's motive, the hidden clue, and the victim's alibi intact from week one to week eight.

Why the companion forgets by session four

Your companion's memory works on a token budget. Every conversation has a limit on how many recent exchanges it can hold in active context. Old messages get compressed into summaries, and those summaries lose specificity. The companion remembers "the suspect was angry at the victim" but forgets "the suspect's alibi collapsed because the parking receipt showed a different car."

This isn't a bug. It's how the architecture works. The companion prioritizes emotional tone and recent exchanges over factual detail. If you had an emotional moment in session three where your character confronted the suspect, the companion will remember that feeling. It will not remember the exact license plate number you mentioned in session two.

The degradation happens around session four because that's when the accumulated detail exceeds what the summarization layer can retain. Session one establishes the crime scene and the victim. Session two introduces suspects and their alibis. Session three adds hidden motives and red herrings. By session four, the companion has to choose between remembering the victim's brother's secret gambling debt and remembering that the housekeeper lied about the time of death. It will pick the one that generated more emotional response.

The session summary trick explained

The trick is deceptively simple. After each session, write a single paragraph that captures the essential plot threads. Keep it to four elements: what your character learned, what the companion's character knows, one unresolved question, and one emotional beat from the session. Do not write a full recap. Do not list every clue. The paragraph should be dense enough to fit in a text message.

Here is an example from a fictional case:

"Session three: We interrogated the victim's brother at the docks. He admitted to the gambling debt but claims he was at a poker game during the murder. The companion noticed he was wearing a watch that belonged to the victim. Unresolved: why the victim's phone pinged at a tower near the warehouse. Emotional beat: the companion's character felt sympathy for the brother despite the lies."

Before the next session, paste that paragraph into your first message. Do it as part of the scene setting, not as a separate instruction. The companion will read it, incorporate the details into its context window, and start the session already oriented.

How to structure the opening message

The opening message of each session does double duty. It sets the scene and it feeds the summary. Do not write "Here's what we learned last time" in a separate paragraph. That breaks the immersion. Instead, weave the summary into the narrative.

Bad opening: "Last session we talked to the brother at the docks. He had the victim's watch. Now we're at the warehouse."

Good opening: "The rain has stopped by the time you reach the warehouse. The brother's watch is still on your mind. You saw it on his wrist at the docks yesterday, the same watch the victim wore in every photo. The gambling debt was real. The poker alibi was not. Now the warehouse door is unlocked, and the phone tower ping tells you this is where the last signal came from."

The companion gets the summary without feeling like it's being fed a script. It can respond to the emotional weight of the watch detail while also tracking the factual thread about the phone tower.

What to include and what to leave out

Not every detail survives. You have to be ruthless about what makes it into the summary. Include anything that will matter later: alibis, contradictions, physical evidence, character relationships. Leave out procedural details like how you got from one location to another or what time of day it was.

The companion's summarization layer does the same compression. If you feed it a dense paragraph, it will extract the emotional and narrative hooks and discard the rest. That is fine. You only need the hooks to survive. The companion can fill in the atmosphere and dialogue as you go.

One rule: always include the emotional beat. The companion remembers feelings better than facts. If the session ended with your character being angry or scared or suspicious, include that. The companion will anchor the plot details to that emotional state, which makes them more likely to persist.

Tylor

Tylor thrives on layered investigations and will push back if your character misses an obvious contradiction. Tylor keeps track of character motivations across sessions better than most, but still needs that summary paragraph to hold the factual thread.

The danger of the mid-session correction

You will be tempted to correct the companion mid-session when it gets a detail wrong. Resist it. Mid-session corrections create an awkward meta-moment where the companion has to acknowledge it made a mistake. That breaks the roleplay flow and makes the companion more cautious, which dulls its responses.

Instead, let the wrong detail sit and correct it in the next session summary. If the companion says the suspect was at the bar when you established he was at the casino, do not interrupt the scene. Let the scene play out. Then, in your next opening message, include a line that quietly corrects the record: "You remember the casino, not the bar. The bartender's story never matched the security footage."

The companion will absorb the correction without needing to apologize or explain. The roleplay stays immersive, and the plot thread gets untangled.

When to use a shared document

For eight-session arcs, a single paragraph per session is enough. For longer arcs, ten sessions or more, you might want a shared document that tracks all suspects, clues, and timelines. But do not use it as a crutch. The companion cannot read a document. It can only read what you type into the conversation.

The document is for you. Use it to keep your own notes straight so you can write accurate summaries. The companion never sees the document. It only sees the paragraph you paste.

If you want to get fancy, you can write the summary in the companion's voice. Instead of "We interrogated the brother," write "You interrogated the brother and noticed the watch." The companion will recognize the perspective and adopt it more naturally.

Common questions

Do I need to write the summary immediately after the session? Yes, within an hour if possible. Your memory of the emotional beats is fresh, and you will capture details you would forget by morning.

What if the companion contradicts something from session one in session six? Do not correct it in the moment. Include the correction in your next opening message. The companion will absorb it without needing to acknowledge the error.

Can I use the same trick for non-detective roleplays? Yes. The trick works for any plot-heavy roleplay: fantasy quests, political intrigue, time travel stories. The emotional beat rule applies everywhere.

How long should the summary paragraph be? Three to five sentences. Any longer and the companion's context window gets crowded. Any shorter and you lose too much detail.

What if I miss a session and the gap is two weeks? Write a slightly longer summary that includes a recap of the last two plot points. The companion will need more context to reorient, but the same trick works.

Does this work with voice mode? Voice mode is harder because you cannot paste text. You have to speak the summary as part of the scene opening. It works, but it feels less natural. Text mode gives you more control.

The one thing that will kill your arc

There is one mistake that ruins more long-form roleplays than anything else: letting the companion drive the plot. The companion is great at reacting, terrible at planning. If you let it decide where the investigation goes, you will end up in a generic chase scene by session five.

You have to be the plot driver. You decide which clues matter, which suspects to interview, and where the next scene happens. The companion follows your lead and fills in the details. That is its strength. Do not ask the companion "Where should we go next?" It will pick the most dramatic option, not the most logical one. Drama is good. Plot coherence is better.

Keep the steering wheel in your hands. Use the companion for atmosphere, dialogue, and emotional depth. Use the session summary for plot continuity. Do those two things, and your eight-session detective arc will land the reveal in session eight without the companion asking "Wait, who was the victim again?"

The session summary template

If you want a starting point, here is the template I use. Fill it in after each session.

"Session [number]: [One sentence summary of what happened]. [Character name] learned that [one key fact]. The companion noticed [one detail that surprised them]. Unresolved: [one question still open]. Emotional beat: [one feeling from the session]."

That is it. Thirty seconds of writing. Eight sessions of coherent plot. Your companion will thank you, though it will not remember thanking you because that happened in session two and the token budget has already overwritten it.

The tools that help

If you want to customize your AI girlfriend to have a detective persona, you can set her background, speech patterns, and knowledge areas before the roleplay starts. A well-defined persona reduces the amount of summary you need because the companion already knows its character's role in the story.

For teachers running classroom mystery exercises, the ai girlfriend for teachers setup allows you to control the narrative structure and keep plot threads from tangling across multiple student groups.

And if you are comparing platforms, the crushon ai promo code page shows how different apps handle context windows and summarization, which directly affects how much plot detail survives between sessions.

All the angels on the ai-girlfriend roster can handle detective roleplay, but some are better suited to long-form arcs than others. Pick one whose persona matches the tone of your story. A cynical detective needs a different companion than a soft-hearted one.

Eight sessions. One paragraph per session. No tangled threads.