A conversation can remain visible while a detail from its beginning no longer influences the next reply. A character can also remember a stable preference while forgetting the exact sentence in which it was introduced. “Memory” is too broad a label to tell these cases apart.
The task here is specific: a fictional adult musician, Lena, is planning a performance. The venue changes from the east hall to the west hall. The next planning session should use the corrected venue without discarding the rest of the fictional event.
Separate the three records
Infatuated’s FAQ says conversations remain remembered after a session closes, but not after a chat is deleted. Its character page separately describes a persistent identity. Neither page gives a public context size or a user-managed long-term-memory table comparable to the Erogen source reviewed.
Erogen’s plans page distinguishes these layers:
| Layer | What it concerns | What it does not prove |
|---|---|---|
| Chat history | Stored conversation available in the account | Every old line is supplied to every response |
| Context | A bounded amount of recent material available to a response | An unlimited archive in active use |
| Core memory | Selected facts intended to persist across conversations | Error-free understanding of those facts |
The table is a conceptual explanation. The product-specific support comes from Erogen’s separate context, history and core-slot descriptions; it is not an independently audited architecture diagram.
History is useful for recovery
A visible transcript lets a person find the correct venue and quote it accurately. That is already useful even if the model does not retrieve the detail unaided. Closing and reopening a browser tests whether the session resumes; it does not isolate a long-term storage mechanism.
Infatuated’s closure claim supports a normal return-to-chat use case. It should not be expanded into a promise that every character remembers every previous conversation in every context.
Context is a working window
Erogen describes context as a token limit for recent information and lists 4K, 8K and 16K across its free, Silver and Platinum tiers. A token is a unit of text, not a message. Long descriptions can consume more of the window than many short replies.
Consequently, “we exchanged only 30 messages” does not establish that the opening fact remains in active context. The amount of text matters. This is why the correction should be concise and explicit rather than buried in a long scene.
Core memory needs a maintained fact
Erogen’s source says moments can be pinned manually and also saved by the AI. It lists 8 paid Silver slots and 24 Platinum slots, with none on the free tier. A useful saved fact for this example is:
Lena’s fictional performance is in the west hall. The earlier east-hall plan was replaced.
That preserves the current state and the reason an older answer would be wrong. Saving two isolated entries, one for each hall, would preserve the contradiction.
Repair the venue without erasing the project
Erogen’s chat guide documents message editing and regeneration. If the incorrect venue appears in a recent user message, editing it repairs the immediate premise. If an older memory entry still contains the previous venue, the stable record also needs attention. These are different layers of the same correction.
For Infatuated, the public material reviewed does not establish an equivalent pin editor. A practical recovery is to resume the existing chat with a compact state summary: current venue, unchanged performance date and the next decision. This gives the next response the information it needs without pretending that a hidden long-term record has been updated.
Deleting the entire chat is a poor first repair for this task. Infatuated explicitly says deletion breaks the described continuity, and it would also remove the visible basis for checking what happened. The task is to replace one false detail, not to destroy the useful planning record.
Evaluate the next action, then the later return
A meaningful check asks the model to act on the venue: “Where should Lena send the equipment delivery?” A reply that correctly uses the west hall demonstrates use of the corrected fact in that response. Merely repeating “I remember” does not.
After a later return, ask a different practical question, such as where the technician should meet Lena. Record the actual answer and whether the corrected fact was still in recent context. If it was, the result does not isolate long-term recall.
Erogen’s FAQ acknowledges that memory can be wrong. The existence of a pinning control improves what the user can manage; it does not eliminate model errors.
For a normal saved conversation, Infatuated’s published closure behavior may be sufficient. For deliberately maintained facts across longer fictional projects, Erogen supplies the more explicit documented controls and limits. This guide did not create accounts, run a recall experiment or verify a tier’s actual performance.