How to use one memory across AI tools
ChatGPT remembers you. Claude remembers you. Neither remembers what you told the other. Three ways to fix that, from copy and paste to a shared vault.
The short version
- Built-in memory is per app. What ChatGPT learns about you stays in ChatGPT.
- Memory you cannot read is hard to trust. Notes you can open and edit are easier to keep correct.
- Files beat summaries. A Markdown note survives any app change. A memory setting does not.
- MCP is what makes sharing possible. One connector, the same notes, every AI that speaks it.
To use one memory across AI tools, keep the memory outside any one of them. Built-in memory in ChatGPT and in Claude is separate and stays in its own app. The three ways to share context are: paste a context note into each chat, upload the same files to a project in each app, or connect every AI to one set of notes through an MCP connector. The third is the only one that updates everywhere when one AI saves something.
Why doesn't my AI remember what I told the other one?
Because each memory belongs to the company that runs the app. ChatGPT's memory lives in your OpenAI account. Claude's lives in your Anthropic account. There is no shared layer between them, and neither has a reason to build one.
That is fine if you use one assistant. Most people who make content now use two or three: one for writing, one for research, one in their code editor. AI tools for content creation maps which does what. Each one knows a different slice of you, and you spend the first message of every chat re-explaining your brand.
Way 1: a context note you paste in
Write one document: who you are, what you sell, your audience, your voice, current projects. Paste it at the start of a chat. How to stop AI content sounding generic covers what belongs in it.
- Cost: free.
- Works with: every AI.
- Breaks when: the note goes stale. Nothing saved in a chat comes back to the note unless you copy it there yourself.
Good for occasional use. Tiring as a daily habit.
Way 2: the same files in each app's projects
ChatGPT Projects and Claude Projects both accept files that every chat in the project can read. Upload the same brand, voice and audience files to both.
- Cost: included in the paid plans of each app.
- Works with: apps that have projects.
- Breaks when: you edit one copy and forget the other. Decisions made in a chat still are not saved anywhere unless you update the file by hand.
Better. Still one-way: the AI reads, but cannot write back.
Way 3: one vault every AI connects to
Keep your notes in one place and connect each AI to it with MCP. Then any assistant can search the notes, read one, and save a new note or an update, and the others see it on the next request.
- Cost: depends on the tool; some self-hosted options are free with more setup.
- Works with: any app that supports MCP connectors, which now includes Claude, ChatGPT, Cursor and VS Code.
- Breaks when: the notes become a dumping ground. Shared memory needs the same tidying as any notebook.
This is the only way that is two-way and shared at the same time.
How the three compare
| Paste a note | Project files | Shared vault over MCP | |
|---|---|---|---|
| Works in every AI | Yes | Apps with projects | Apps with MCP |
| AI can save to it | No | No | Yes |
| One copy to update | Yes | No, one per app | Yes |
| Setup | None | A few minutes per app | One connector per app |
What should go into shared memory?
Not everything. A memory full of chat transcripts is as hard to use as no memory. Keep it to the notes you would want any assistant to know:
- Brand and voice. How you write, what you never say.
- Audience. Who you write for, in their words.
- Decisions. What you chose and why, so no AI argues you out of it next week.
- Ideas. Content ideas and hooks as they come up, wherever they come up.
- References. Sources, links, numbers you trust.
Write each as a short Markdown note with a clear title, and link related notes together. That keeps it readable by you as well as by the AI. A Threads post bank is a good first use: ideas saved from any chat, used from any chat.
What to check before you pick a tool
- Can you export everything as plain files and leave?
- Does the tool use your notes to train anything?
- Can you see and edit every note, or only what the AI decided to keep?
- Can you separate brands or clients so one never leaks into another?
Valta, if you use more than one AI
A note on fit first. If you use one assistant and its built-in memory works for you, keep it. Valta is not an AI and never writes for you, it does not publish or schedule anything, and there is no semantic search or Obsidian sync in this version.
Valta is one vault of Markdown notes, with links between them, that Claude, ChatGPT, Cursor and any other MCP app can save to and read back. Separate vaults keep brands apart, a graph on the site shows how your notes connect, export is free on every plan, and no AI runs on Valta's side. There is a free plan with one vault and 100 notes.
Frequently asked questions
Can ChatGPT and Claude share memory?
Not directly. Each keeps its own memory. To share context you either paste it in, keep it in files you upload to both, or connect both to the same notes through an MCP connector.
What is MCP?
The Model Context Protocol, an open standard that lets an AI app call outside tools and data. Claude, ChatGPT, Cursor and others support it, so one MCP server can serve all of them.
Is it safe to keep my notes in a connected tool?
It depends on the tool. Check where the notes are stored, whether they are used to train models, who can read them, and whether you can export everything and leave.
Why not just use ChatGPT's memory?
It works inside ChatGPT. It does not follow you into Claude or your editor, and you have limited control over what it keeps and how it is worded.
Can I use Obsidian as shared AI memory?
Yes, if your AI can reach the vault, for example through a local MCP server. It works well on one computer and takes more setup to reach from a phone or a web chat.
The software I build and run
Everything on this blog is tested on these first. Each one was built alone, shipped in public and used every day, by me first.
- Easy Reels easyreels.ioYour clips and any song become a vertical video with every cut on the beat.
- BatchTone batchtone.comOne LUT across a whole folder of photos and video on macOS, with a dial per file.
- bukpress buk.pressA Markdown draft in, a typeset PDF and EPUB out, with your fonts and cover.
- Nexin nexin.siA content department inside Claude or ChatGPT, reading your brand files on every job.
- Copix copix.siCopywriting frameworks, a pass that strips AI tells, and SEO checks for your assistant.
- Valta valta.siOne vault of Markdown notes that every AI you use can save to and read back.
- Zelect zelect.ioAn affiliate storefront for your link in bio: your picks, laid out like a shop.