Back to Adamant

Transfer ChatGPT memory to Claude, Codex, and other AI tools

If your best context is trapped in ChatGPT but today you are working in Claude, Codex, Claude Code, Cursor, or Gemini, you need retrieval portability rather than another long pasted summary.

Short answer: Adamant is designed to import conversation exports, normalize them into canonical memory records, and retrieve the few snippets another model needs. This does not train the next model; it gives the model cited context for the active task.

Why direct memory transfer is hard

AI platforms store memory and project context in their own product boundaries. ChatGPT history does not automatically become Claude memory. Claude Project knowledge does not automatically become Codex repo context. Gemini conversations do not automatically become local RAG.

Adamant's cross-model pattern

SourceAdamant stepDestination
ChatGPT exportParse into canonical records, chunks, graph objects, and vectorsClaude, Codex, Claude Code, Cursor, Gemini, local models
Claude notes or project decisionsStore as cited project memory with provenanceCodex, local CLI retrieval, future model sessions
Markdown or Obsidian notesNormalize and index alongside conversation memoryAny model that can receive retrieved context

Example handoff to Claude Code or Codex

python -m adamant context "what ChatGPT decisions matter for this repository?" \
  --mode local \
  --top 5 \
  --max-tokens 1200 \
  --format markdown

What to ask when a model forgets

Important privacy boundary

Adamant should retrieve only the context needed for the current task. The destination model does not need the full export. Before personal data is used, test with synthetic data and confirm sanitization, RLS, and deployment checks pass.

Related guides