Resetting an AI companion can fix stale memories, unwanted relationship behavior or a profile that has accumulated too many incorrect assumptions. It can also remove months of useful context if you press reset without a backup. Before changing memory or relationship state, save the information that would be difficult to reconstruct later.

Export the conversation archive

If the app supports export, download your chat history before resetting. A readable HTML or PDF copy is useful for reference, while structured JSON is better if you may process the data later.

Open the archive once before continuing. A backup that cannot be read is not useful after the original account state has already changed.

Save visible long-term memories

Open the memory manager and copy important stable facts such as preferred name, language, ongoing goals and meaningful relationship milestones.

Do not assume these items are fully represented in the chat transcript. Many apps store memory as separate summarized records.

Write a one-page relationship summary

Record the companion’s role, preferred tone, important boundaries, major shared events and anything you would want a fresh version to understand immediately.

This summary is far easier to reuse than thousands of messages and lets you choose what deserves to survive the reset.

Record behavior settings

Relationship mode, proactive-message frequency, notification preferences, nicknames and voice selection can all influence how the companion feels.

Take screenshots or notes so you can tell whether the reset changed memory, settings or both.

Separate what you want to keep from what caused the reset

If the problem is one unwanted nickname or stale topic, do not automatically bring that memory back. Make a small “do not restore” list before resetting.

This turns the backup into a curated migration rather than a complete copy of every old assumption.

Test the new state before deleting the backup

After reset, ask a few neutral questions and confirm the old unwanted behavior is gone. Then restore only the most important context.

Our AI companion memory correction test can help verify whether the new memory state behaves as expected.

A reset should give you a cleaner relationship, not force you to lose everything valuable. Backing up chats, durable memories and relationship settings lets you remove the problematic state while keeping control over what continuity you choose to rebuild.

After the reset, do not immediately re-import everything. Start with the small relationship summary and only the durable facts you still want the companion to know. This gives you a cleaner baseline and makes it easier to see whether the old problem was caused by one stale memory, a relationship setting or a broader account issue. If the reset solves the problem, you can add important context back gradually instead of recreating the same overloaded memory state on day one.

Decide what continuity you actually want to keep

Before resetting a companion, separate explicit profile preferences, important saved memories, selected conversation history and media created during the relationship. Users may wish to remove a sensitive period while preserving language settings or ongoing projects; an all-or-nothing export may not offer that control.

Check whether the service provides a readable memory list or only a raw transcript. Derived summaries may not be included in a conversation export, so the difference should be clear.

Test restoration without reviving unwanted data

A backup is useful only if the receiving account or service can restore the intended information accurately. Preview the export, remove obsolete or private details and distinguish historical facts from current preferences.

After reset, verify that old memories marked for deletion no longer influence recommendations or replies. This matters because visible chat deletion may not automatically clear every stored preference or retrieval index.

Backing up a conversation is not always enough to recover relationship continuity. Some services store stable memories, pinned facts and derived summaries separately from visible transcripts. Before resetting, check whether those layers are included in the export and whether the user can exclude specific information.

A good reset test also distinguishes “remove this memory” from “forget this chat.” The system should explain whether the two actions have the same scope. Otherwise a detail the user intentionally deleted can reappear later through an old summary or another device.

A reset should be reversible only where the service explicitly supports it. Users should not assume that a backup can restore every private conversation or generated asset after deletion. Exporting key memories and media in an understandable format before taking an irreversible action is therefore a practical safeguard.