AI Companions
Why Your AI Companion Forgets: Checks Before You Reset the Chat
Troubleshoot an AI companion that forgets names, story details or voice calls. Check memory settings and preserve your chat before resetting anything.
by NSFW-Tools · 6 min read
An AI companion may forget because a detail was never saved, memory access is disabled, or the conversation or interaction mode changed. A missed detail does not always mean the chat was deleted. Preserve your setup, then check one harmless fact while changing one setting at a time.
The steps below can help you find a settings problem or document a useful support request. They cannot guarantee recall or establish whether a provider has a model fault. Check your app's current help pages before following a menu path, since providers change these controls.
Preserve your setup before troubleshooting
Copy your character setup and the facts you want to keep into a private note. Record the conversation name, selected model and the last date recall seemed correct. Use an export option if your app offers one.
Avoid posting a full intimate conversation to a public support forum. Share a short, fictional example that reproduces the problem instead.
Use this checklist to choose your first check:
| You notice the problem after... | Check first |
|---|---|
| Opening a new conversation | Whether memories carry between conversations |
| Moving from text to a call | Whether the app shares history between those modes |
| Updating a saved fact | Whether an older, conflicting entry remains |
| Resetting or clearing history | Which records the confirmation said it would remove |
| Changing the model or plan | Whether you also changed a memory option or limit |
1. Confirm that you opened the same conversation
Return to the thread where you established the missing detail. Check the thread name and the companion you selected before adding more memories or changing models.
Nectar says new conversations do not inherit earlier memories. Archive preserves them; Reset deletes them. Check this distinction before starting over. Nectar's memory guide
Do not assume another app follows the same rules. Find its description of new chats, duplicates and archives. An app may reuse a character's setup while keeping separate conversation histories.
2. Check memory access and memory creation
Open the memory panel and check whether it contains the fact you expected the companion to recall. A blank list needs a different response from a list containing an incorrect entry.
Nectar separates Enable Memory from Automatic Creation. Check both switches and their access requirements before assuming saved facts are being created and used. Nectar's memory controls
Record the existing settings before changing them. Check whether the app asks for payment, uses credits or restricts a control to a plan. A troubleshooting attempt should not turn into an unplanned upgrade.
3. Correct one saved fact, then test it
Use an invented scheduling puzzle: “In our fictional city, the museum is closed on Wednesdays.” Do not include its answer in your later test question. This lets you check whether the reply draws on a saved fact instead of merely repeating the prompt in front of it.
Nectar documents 200-character custom entries and up to ten high-importance memories. Custom-memory instructions
Later ask it to choose a museum day from Wednesday or Thursday. Record whether it chooses a valid day and why. Try a second independent fact after other conversation. One correct response is useful evidence, but it does not measure recall reliability across weeks.
Keep the test fictional. You do not need to disclose an address, medical history or other sensitive information to check whether a memory setting works.
4. Check the text-to-call boundary
If recall changes during a voice call, inspect call settings before rewriting the companion's backstory.
Kindroid's guide, updated October 13, 2026, describes a Shared chat history control for continuity between text and calls. It also states that long-term-memory recall is paused during calls, although calls can form new long-term memories. A fact available in text may therefore need different handling on a call. Kindroid's call-memory documentation
Try the same neutral question in text and in a call, then record the difference. Add a brief recap when switching modes if needed. Avoid changing the voice, model and memory controls together, because you would lose track of which change helped.
5. Read the reset confirmation before using it
Treat Reset, Clear history and Chat break as separate actions until the provider explains them.
Kindroid says a chat break keeps existing cascaded memories by default. Selecting Reset Cascaded Memory clears that continuity. A reset intended to fix an awkward reply can therefore remove context you wanted to preserve. Kindroid's memory guide
Copy the details you need before confirming a destructive action. If your app provides no clear description of what a reset removes, ask support first. Do not use repeated resets as a way to test whether memory improves.
6. Check whether an update applies to old memories
A provider may improve how it creates new memories without rebuilding existing ones. Read the release note's scope before expecting old errors to disappear.
Nomi's August 25, 2026 announcement states that its memory-formation changes were not retroactive and might take more than 100 messages to become noticeable. That describes one update, not a universal number of messages required to fix memory. Nomi's memory update
Compare the date of your problem with the update history. Keep a small test log instead of rebuilding your character each time a provider announces a new model.
7. Send support a reproducible example
Include the model, device and app version, plus the relevant memory setting. Show the saved fictional fact, your test question and the reply that ignored it. Note whether text and calls behave differently.
Describe the expected result: “The saved entry says the museum is closed on Wednesdays; I expected the plan to use Thursday.” This gives support something more precise than “the memory is broken.”
Use our guide to how AI companions work for background. If you use Nectar, the Nectar AI profile provides another starting point for checking the product's current features.
Frequently asked questions
Does paying for a higher plan fix forgetting?
A higher plan may offer additional capacity or controls. Check the specific change before paying. More capacity does not prove that the app will recall the fact you care about. Test the existing settings and review conflicting entries first.
Should I keep repeating the missing fact?
Use a brief correction to continue the conversation, then inspect the saved record. Repeating an obsolete fact alongside a corrected version can make your own troubleshooting harder. Keep one clear current version wherever the app lets you edit memories.
Can I reset a chat without losing memories?
That depends on the app and the action. Read the confirmation and preserve a copy first. A provider may separate a chat-history reset from a memory reset, while another may remove both together.
Why does my companion remember in text but forget on a call?
Check whether the app shares conversation history across modes and whether it documents call-specific limits. Test the same harmless fact in each mode. A voice call and an audio reading of a text reply may use different settings.
Can I prove memory works with one successful answer?
One answer establishes one successful response. Try related questions across later exchanges and record the conditions. Avoid claiming a permanent fix until you can reproduce the improvement without feeding the answer into each question.
Platforms mentioned in this post
Tap any one for the full review.
