Step zero
Don't do anything yet
If you just realized your memory is gone, the strongest thing you can do in the next thirty minutes is not clear any other data. Do not "log out and back in." Do not delete conversations to "test whether it comes back." Do not clear browser storage. Every action reduces the surface area of the recovery.
Diagnosis
What actually happened?
Four possibilities, in decreasing order of frequency.
1. Silent eviction
You hit the per-account memory cap and ChatGPT dropped the oldest entries. Symptoms: some memories still visible in Settings → Personalization → Memory, but the earliest few are gone.
2. Feature rollout / rollback
OpenAI changed how memory works. Symptoms: memories list looks reorganized or empty; a banner appeared recently in the app.
3. Self-deletion by mistake
You clicked "Clear all" or an individual delete. Symptoms: empty memory list, no banner. No server-side backup exists for this one.
4. Account issue
Billing, family sharing, or a plan change (e.g. downgrading from Plus to Free) reset the account context. Symptoms: you're signed in but nothing looks familiar; check the account email — it may have shifted.
Recovery
The recovery ladder
Work top-down. Stop at whichever rung gets you back.
- Wait 24 hours. Roughly 15% of "my memory is gone" reports self-resolve within a day when the cause was a rollout hiccup.
- File a support ticket. Help center → chat with support. Ask specifically: "Was there a memory-service incident affecting my account on [date]? Can memory be restored from a server-side snapshot?"
- Retrieve your export. When the ZIP arrives, open
user.json. If it lists saved memories, you have a snapshot to work from. - Re-inject. Copy the salient memories back into Custom Instructions ("What would you like ChatGPT to know about you"). This isn't identical to the Memory feature, but it's read on every turn.
- Reconstruct. If none of the above land, proceed to the next section.
Reconstruction
Reconstructing from the exhaust
Even without memory, you almost certainly have exhaust — the side effects of having used ChatGPT for months. Mine it:
- Conversation history. The transcripts are still there for 30 days after any deletion. Skim the last three months. Note recurring context (projects, people, preferences). Feed the digest back into Custom Instructions.
- Your own writing. Anything you wrotebecause of a ChatGPT conversation — a draft email, a code file with a "// ChatGPT helped" comment, a journal entry — is proof-of-context you can re-teach.
- Screenshots. The "Manage memories" screen was the source of truth. Search your photos for screenshots of it; most heavy users have at least one.
Reconstruction is emotional labor as much as technical. Give it a Saturday. It gets easier if you sit with the question what does this AI need to know to be useful to me next week? rather than what did it used to know?.
Prevention
Preventing it next time
Three habits, ordered by cost-to-benefit.
- Monthly export. Set a calendar reminder for the first of the month: Settings → Data Controls → Export data. Overwrite last month's file.
- A one-page "instructions" doc. Everything important, in your own words, in a plain-text file you can paste into any assistant. Update quarterly.
- A sidecar vault. If your ChatGPT history is load-bearing, keep a second copy somewhere the provider can't touch. That's what Konshus exists to do.
FAQ
Frequently asked
Frequently Asked Questions
Further reading
The naming ritual
Now name yours.
Every Konshus starts with a name. Pick one and watch your AI's voice come to life — preserved across every model switch, export, and reset.
Name Your Konshus