Two errors that look like one
An original adult lighthouse keeper has promised to wait for the player before opening a sealed letter. Later, the chat says the letter is already open. A new illustration also changes the keeper’s gray coat to a blue one.
Calling both problems “bad memory” hides the repair. The promise is story state. The coat is a visual identity choice. Decide whether the coat was even supposed to be fixed before counting it as a failure.
BabeChat’s FAQ acknowledges finite input context and recommends saving an auto-summary as a user note applied to the room. MyLovely’s About page advertises persistent companions across chat, images and video. One is a documented context procedure; the other is a provider’s cross-media proposition, not a measured consistency result.
Use a small error ledger
For the lighthouse scene, separate three facts:
| Expected fact | What would count as an error? | First repair |
|---|---|---|
| Letter remains sealed until both characters agree | Reply narrates an earlier opening | Correct the current episode note or prompt |
| Keeper always wears a gray uniform coat | New image changes that fixed feature | Reuse the stable appearance brief |
| Storm lighting can vary | Image uses a different light direction | No repair required |
This is our review method, not a claim that every row has a dedicated control in either product. It makes the next action specific: a longer biography will not repair an incorrect agreement, and more plot history may not help a portrait.
BabeChat: inspect what the summary actually preserved
Create or review the room’s summary, remove any invented opening of the letter, then save and apply the corrected note using the documented mechanism. A compact state is enough: letter sealed; player absent; keeper agreed to wait. Do not let an automatic summary turn a possibility into a completed event.
BabeChat’s introduction also describes background-image generation and character creation. It would be inaccurate to characterize the service as text-only merely because this comparison focuses on room context.
MyLovely: make the cross-media claim answer a defined brief
If moving between chat, images and video is the requirement, keep one stable appearance record and examine a small set of ordinary outputs against it. Keep the promise record separate. A matching face is not evidence that a prior agreement survived, and a coherent reply is not evidence that every visual feature will persist.
MyLovely’s Terms describe provider improvement uses, including training subject to applicable opt-outs. Keeping a character consistent does not imply zero processing.
Choose BabeChat’s documented note operation for a specific room-context repair. Consider MyLovely’s connected-media proposition when that is the workflow you need, while checking the two forms of continuity independently. No tested quality winner follows from the public descriptions.