ChatGPT remembers your name and tone beautifully. Stop being its long-term memory.
ChatGPT memory lives inside one app, on one vendor’s terms - and Claude never hears a word of it. Naumu is the long-term brain your assistants share: dump your pile, it builds a real connected map, and your ChatGPT writes the same graph Claude reads - acting as you, every change one tap to undo.
Why Naumu holds up
One portable brain your assistants read and write.
Your AI authors it, not just recalls it
ChatGPT memory updates its own list inside ChatGPT. Over MCP your assistant writes to a real graph that belongs to you - acting as you, one tap to undo - and Claude reads the exact same brain the next morning. One memory, every assistant, not a silo per vendor.
Every answer has a receipt
A remembered fact in ChatGPT doesn’t carry where it came from. Naumu stamps every node with its source and the timestamp it was captured - click any claim and the row it came from opens, including the ones your assistant wrote.
Keep ChatGPT. Connect it. Run both.
You don’t leave ChatGPT - you point it at Naumu over MCP (setup at /docs/chatgpt). Keep its built-in memory for tone and chat feel; let Naumu hold the structured, cross-assistant brain. Switch fully only once it’s earned it.
Watch it work
Monday went into ChatGPT. Tuesday, Claude quotes it back.
Monday you dump a launch slip into ChatGPT mid-conversation - date moved, vendor blocking, a “don’t announce yet” rule - and Tuesday you open Claude, a different assistant, to draft the announcement.
Tuesday’s question never says “Stripe” or “July 10” - the answer is the path across the links, not a keyword match. Scripted so you can see the shape - paste your own below and ask.
The honest comparison
Where each tool actually wins.
Here’s the real split - including the rows ChatGPT memory wins outright.
Shared across Claude AND ChatGPT
No - memory lives inside ChatGPT; Claude never hears it.
Both read and write the same graph over MCP, as you.
Writes back to a real knowledge base
Memory updates its own internal list - not a knowledge base you own.
Two-way over MCP - your assistant writes the graph directly, every change one tap to undo.
Structure
A running list of remembered facts.
A real typed graph - entities and relationships you can open, traverse, and ask.
Where a fact came from
You can view and edit saved memories, but a fact doesn’t carry its source.
Every fact traces to its source, with when it was captured or last updated.
Capacity
Bounded saved memories plus chat-history reference - still inside one app.
Your graph grows with you - no memory slots to ration (free tier caps at 1,500 nodes).
Carrying context across chats
Within ChatGPT, yes - its memory and history stay in ChatGPT.
One persistent graph - the same brain every session, every assistant.
A failed write tells you it failed
n/a - there’s no external write to fail.
A failed MCP write surfaces an error on that turn; the agent never ends pretending it wrote.
Owned and portable
Lives inside ChatGPT, on OpenAI’s terms; leaves when you do.
Yours and vendor-neutral - swap which assistant you trust without re-teaching it your life.
Remembering your name, tone, and how you like answers
Best-in-class - and the right, free tool for exactly that.
Overkill if personal chat feel is all you want.
Zero setup - open a tab and start, nothing to wire
Nothing to connect; memory just turns on inside ChatGPT.
You connect an assistant once over MCP (setup at /docs/chatgpt).
Trying it
Already on if you use ChatGPT - nothing to try separately.
No signup to try - the map builds in front of you; Keep it (one tap, no email) if it earns it.
If all you want is for ChatGPT to remember your name, your tone, and how you like answers phrased - its built-in memory is the right, free tool, and you shouldn’t bolt a knowledge graph onto that. Naumu is for the other thing: re-pasting your context every morning and wishing Claude knew what you told ChatGPT. That gap is what it’s built for.
Better together
Try Naumu with the ChatGPT you already use.
This isn’t a switch at all - it’s a connection. Point ChatGPT at Naumu once over MCP (setup at /docs/chatgpt, about a minute) and keep chatting exactly where you chat. ChatGPT keeps its built-in memory for your tone; Naumu becomes the structured brain it reads and writes underneath.
It reads AND writes, as you
ChatGPT acts with your exact permissions - it drops facts into the graph mid-conversation and answers from it, every change one tap to undo.
Claude hears it too
Whatever ChatGPT writes on Monday, Claude reads on Tuesday - one shared memory across assistants, not a silo per vendor.
Keep both memories
ChatGPT’s built-in memory stays on for name and tone; Naumu holds the structured, sourced knowledge that has to outlive any one vendor.
FAQ
Adding Naumu to ChatGPT.
Compare Naumu with other tools
Stop being the clipboard. Start asking.
Drop your pile or bring your ChatGPT export, connect your assistant once over MCP, and give your AI a brain it can actually keep - and write to.