Import existing conversations
Local coding sessions, vendor export files, and one-off browser capture: what Mem can pull in today.
Mem can bring in prior chats in three ways: coding agents we discover on disk, files you export from an app, and the browser extension on the tab you are looking at. This page matches those options to the buttons in Threads → Import (and Connectors → Thread Import).
Threads reference
Bulk filenames, Markdown headers, and odd edge cases live in Threads.
Pick what matches you
| You have… | In Mem | Notes |
|---|---|---|
| Claude Code, Cursor, Codex, OpenCode, or Proma Chat logs on disk | Threads → Import → Find AI Conversations (same entry under Connectors → Thread Import) | Pick sessions after Mem scans |
| Older local sessions from Antigravity, Claude Code, Grok Build, Codex, Craft Agent, Gemini CLI, Kimi Code, Kimi Work, MiMo Code, OpenCode, OMP, Pi, or Proma, especially when Mem runs on another machine | Run nmem t sync --from ... on the machine where that agent stores its sessions | Preview first; add --apply when the list looks right |
| A full export from ChatGPT, Google Gemini / AI Mode, Claude (claude.ai / Claude Desktop), DeepSeek, ChatWise, Alma, or Raycast AI (via exporter JSON) | Threads → Import → Import account history | One file (see table below) |
One .md thread or similar | Threads → Import → Single Thread | See Single thread |
| A chat open in the browser right now | Browser extension | Sends the focused session from the tab you use with the extension, not your full account history |
Coding agents (disk)
Find AI Conversations looks for local session data from Claude Code, Cursor, Codex, OpenCode, and Proma Chat. Nothing is saved until you choose what to import.
Plugins can also keep threads in sync over time; this scan is mainly for catching up (new machine, or first setup).
For connector history that is not listed in the desktop scanner, use the CLI backfill path. Supported sources today are antigravity, claude-code, grok, codex, craft-agent, gemini-cli, kimi-code, kimi-work, mimo-code, opencode, omp, and pi.
# Project-scoped coding agents
nmem t sync --from codex --all-projects --limit 20
nmem t sync --from craft-agent --all-projects --limit 20
nmem t sync --from grok --all-projects --limit 20
# Pi sessions
nmem t sync --from pi --limit 20
# Other local coding-agent stores
nmem t sync --from antigravity --limit 20
nmem t sync --from kimi-code --limit 20
nmem t sync --from kimi-work --limit 20
nmem t sync --from mimo-code --limit 20
nmem t sync --from omp --limit 20The first run is a preview. Replace codex with another supported source when needed. When the list looks right, run the same command with --apply.
Antigravity history
Current Antigravity CLI and Antigravity 2.0 sessions keep a documented local transcript.jsonl, which nmem t sync --from antigravity reads directly. The command imports only user and assistant turns and keeps the original conversation ID, so it converges with live capture instead of creating a second thread.
Some older sessions exist only in Antigravity's private cache. For those, use the Antigravity Trajectory Extractor while Antigravity is running, export JSON, then preview it with nmem t sync --from antigravity --session-dir <export-directory>. Mem does not guess at private protobuf or database formats.
Remote Mem works the same way
Run nmem t sync on the laptop or server where the AI tool keeps its session files. The command uses your normal nmem client config, so it can upload to local Mem or a remote Mem server. The remote server does not need direct access to your ~/.codex, ~/.craft-agent, ~/.grok, ~/.claude, ~/.gemini, ~/.kimi-code, Kimi Work runtime, ~/.pi, ~/.omp, ~/.proma, OpenCode, or MiMo Code data.
Export files (bulk)
Import account history is the shared entry for ChatGPT, Claude, DeepSeek, and the other supported exports below. Choose the file listed for your app:
| App | File | Export |
|---|---|---|
| ChatGPT | chat.html after you extract the downloaded ZIP | Settings → Data controls → Export data |
| Google Gemini Apps / AI Mode | The Takeout ZIP, or MyActivity.html after you extract it | takeout.google.com → Deselect all → My Activity → All activity data included → select Gemini Apps or AI Mode → export. Do not select the top-level Gemini checkbox; that is for Gems settings, not chat history. |
| Claude | data-…-batch-….zip (contains conversations.json + memories.json) | Web or Desktop: initials → Settings → Privacy → Export data, then Anthropic emails a download link (see their guide). Not available from Claude mobile apps. |
| DeepSeek | deepseek_conversations.json | chat.deepseek.com → Settings → Data → Export data |
| ChatWise | .zip of chats | Export all chats from ChatWise |
| Alma | alma-backup-…zip with threads.json | Settings → Data → Export all threads |
| Raycast AI | raycast_ai_chats.json (or any .json from the tool) | No built-in export, so use raycast-ai-exporter (macOS; see its README) |
Claude, Google Takeout, ChatWise, and Alma files can stay zipped. For ChatGPT, extract the download and select chat.html. Mem figures out the format from the file you choose.
Google Takeout file
For Gemini and AI Mode, Google stores the chat text in My Activity, not in the top-level Gemini export. You can upload the full Takeout ZIP, or extract it and upload Takeout/My Activity/Gemini Apps/MyActivity.html or Takeout/My Activity/AI Mode/MyActivity.html directly.
After a bulk import
Imported conversations are searchable right away as Threads. Mem does not automatically turn every imported conversation into Memories, because a large archive can spend a lot of AI tokens and produce noisy results. Start by searching the imported threads; distill only the decisions, facts, procedures, or lessons you want to keep as long-term memory.
When you do want to process a backlog, go to Threads, click Select, choose the current page or Select all results, then click Plan distillation. Mem plans a small safe wave instead of queuing hundreds of conversations at once; very large threads are deferred for a separate pass.
Claude export ZIP
Use the ZIP from the email (for example data-2026-04-01-08-10-35-batch-0000.zip). Mem imports all chats from conversations.json and saves Claude's profile memory from memories.json as a labeled memory card after the threads you selected finish importing. If you only extract conversations.json, you get threads only.
Raycast AI (macOS)
The exporter is a third-party script: you keep Raycast’s AI Chat window open, grant Accessibility to your terminal, and it writes structured JSON (sessions with role / content messages). Dates in the file are approximate (sidebar groupings). The same JSON works in Import account history and nmem t import --file.
Browser: focused tab only
The extension does not download your entire web chat history. It works with the session in the active tab when you capture, useful for what you are doing now. For everything the provider ships in one archive, use Import account history (or your coding-agent scan where that applies).
Where to click
- Threads → Import: Find AI Conversations, Import account history, or Single Thread.
- Connectors → Thread Import: same story, plus shortcuts into Threads.
Next
- Threads: formats and distillation
- Getting Started: first day in the app
- Connectors: AI tools, MCP, extension