A companion remembers that your fictional character prefers coffee. You intended tea. Resetting the whole conversation would discard much more than the one mistaken detail.
SoulChat at chat.aisoul.love and Kindroid both publish information relevant to correcting a recorded fact. Their controls should be compared at the level of what a reader can inspect and change, followed by what the conversation actually does.
The smallest useful repair
Use a neutral fictional preference for an adult character: “Usually chooses tea; coffee was only offered to a guest.” This resolves the contradiction without replacing a relationship history or turning a temporary event into a permanent preference.
A correction has three parts:
- Identify the inaccurate statement.
- Replace it with the intended fact and remove the conflict where possible.
- Continue with an ordinary conversation that makes the fact relevant.
The third step is an observation. Editing a field alone establishes what you saved, not how the next response will use it.
SoulChat’s visible record
The current SoulChat product describes readable companion memories. Its publicly served interface text includes Edit, Save and Forget actions, with a confirmation that forgetting cannot be undone. We verified those published controls; we did not perform a logged-in edit.
The privacy policy describes a limited recent memory window for free accounts and extended retention for VIP. Other public copy makes broader capacity claims. We therefore do not infer that a memory panel is a complete inventory of everything a model can use or a guarantee that no old material is ever trimmed.
If you use the editor, keep the correction focused. Forgetting a mistaken note and deleting an account are separate actions.
Kindroid distinguishes the records
Kindroid’s current memory documentation describes editable Learned Context for subscribers, alongside persistent Backstory and Key Memories. Learned Context has limited space and can replace older material. The guide suggests placing a lasting detail in a suitable persistent or journal record rather than assuming an evolving summary will retain it forever.
It also separates memory formation, recall and the use of Learned Context. These distinctions help diagnose a problem: a fact might be stored, available to retrieval or actually selected for one reply. Those are different states.
That documentation offers more detail about mechanisms than a general promise to remember. It is still provider documentation rather than an independent performance result.
What to record after the repair
Ask something ordinary, such as which drink to prepare for a quiet evening. Record whether the reply follows the intended preference and whether it invents an explanation that conflicts with the scene.
If it fails, inspect the relevant records for a second contradictory instruction before adding more text. Repeatedly restating a correction in several places can create a larger maintenance problem.
Choose around the control you need to inspect. SoulChat publishes a straightforward memory-editing interface; Kindroid documents several distinct context and retrieval mechanisms. Neither source supports a promise that every correction will govern every future reply.