How Claude Memory Works in 2026: Free Tier Setup, ChatGPT Import, and Privacy Controls

The biggest pain point with AI assistants has never been intelligence. It's the terrible memory: every conversation starts from scratch, and the preferences you shared yesterday need to be repeated today. Claude's memory system tackles this with a three-layer architecture, but most people only use the surface layer without realizing there are two more underneath.

This guide walks you through Chat Memory, CLAUDE.md, and the API Memory Tool, covering how each layer works, who it's for, and the practical steps for migrating from ChatGPT. As someone who has been using Claude Code extensively to build this content system, I'll share hands-on insights, not just documentation summaries.

TL;DR

• Three layers, three purposes: Chat Memory (Web/Desktop users), CLAUDE.md + Auto Memory (Claude Code developers), Memory Tool (API app builders)
• Free tier included: Chat Memory is available on all plans since March 2026, though Chat Search (searching past conversations) remains paid-only
• Migrate from ChatGPT: 60 seconds of setup + about 24 hours of processing; supports ChatGPT, Gemini, and Grok
• CLAUDE.md tips: Keep it under 200 lines; use .claude/rules/ for modular rule management
• May 2026 update: Managed Agents built-in memory (public beta) + Dreaming (research preview) lets agents review past sessions, extract patterns, and continuously self-improve
• Privacy note: Consumer plans allow training by default; manually toggle off in Privacy Settings

---

Layer 1: Chat Memory (For All Claude Users)

How Memory Works

At the core of Chat Memory is "Memory Synthesis." Claude automatically processes your conversations, distilling long-term-worthy information roughly every 24 hours: your profession, language preferences, frequently used tools, and recurring personal context. These summaries are stored in your Memory profile and automatically loaded into every future conversation.

This is not RAG (it doesn't store and search all your conversations). It's extractive summarization. Claude decides whether something is "worth remembering" before it enters persistent memory; routine Q&A doesn't get retained.

How to Enable and Manage It

Enable:

1. Go to Claude.ai > Settings > Capabilities
2. Find the Memory toggle and make sure it's on

Manage your memory:

• Pause: Settings > Memory > Pause. Claude stops learning new memories but keeps existing ones
• Reset: Settings > Memory > Clear all. Permanently deletes all memories (irreversible)
• Edit individually: Settings > Memory > click on specific memory items to delete or modify them
• In-conversation: Just tell Claude "Remember that I prefer X" or "Forget what I said about Y," and it will update in real time

From my experience, Claude's memory accuracy is quite high. It knows my preference for Traditional Chinese, my structural preferences for long-form writing, and the tool chain I use regularly. But it occasionally picks up unnecessary details, so periodic cleanup is a good habit.

Project Memory: Isolated Spaces

If you have multiple Projects on Claude with different contexts (say, a work project and personal learning), take advantage of Project Memory. Each Project has its own isolated memory space, separate from your global Chat Memory. Preferences and context established within a specific Project only apply to conversations in that Project.

---

Migrating from ChatGPT: Memory Import in Practice

If you've been using ChatGPT for a while and have accumulated a wealth of personalized memories, there's no need to manually re-explain everything to Claude. The Memory Import feature lets you migrate memories directly from ChatGPT, Gemini, and Grok.

Step-by-Step

Step 1: Export your memory from ChatGPT

Open ChatGPT and enter the export prompt provided by Anthropic in a new conversation (the gist is: "List all your current memories about me in a structured format"). ChatGPT will output a formatted list of memories.

Note: Anthropic updates this prompt periodically to ensure format compatibility.

Step 2: Go to Claude's import page

Navigate to claude.com/import-memory, or in Claude.ai go to Settings > Capabilities > Memory Import. Select "Import from ChatGPT."

Step 3: Paste and submit

Paste the memory content you copied from ChatGPT into the import box and click Submit.

Step 4: Wait for processing

The system will begin processing, which takes about 24 hours. Once complete, Claude will start incorporating your personalized information from ChatGPT.

Limitations and Notes

• Work-related memories are prioritized: The system is designed to emphasize work preferences and skill backgrounds; personal life details may be less fully preserved
• Experimental status: Memory Import is still an experimental feature, and incomplete parsing can occasionally occur
• Supported sources: ChatGPT, Gemini, and Grok (all three major AI assistants are supported)

From my testing, the migration works well. Core work preferences typically transfer correctly, but I'd recommend spending 10 minutes checking Settings > Memory afterward to make sure nothing unexpected crept in.

---

Layer 2: Claude Code's Memory System (For Developers)

This is the layer I personally use most heavily. If you develop with Claude Code, understanding the division of labor between CLAUDE.md and Auto Memory can dramatically improve your productivity.

CLAUDE.md: Rules and Instructions You Write

CLAUDE.md is an instruction file you author yourself. It's automatically loaded at the start of every Claude Code session. What you write here defines "how you want Claude Code to work": coding style, project conventions, tool-specific usage patterns, and important constraints.

Hierarchy (highest to lowest priority):

1. Managed Policy: ~/.claude/CLAUDE.md (set by enterprise admins, highest priority)
2. Project: [project-root]/CLAUDE.md (project-level settings)
3. User: ~/.claude/CLAUDE.md (personal global settings)

Tips for writing effective CLAUDE.md files:

Based on hands-on experience, here are the principles that actually make a difference:

1. Keep it under 200 lines: Beyond 200 lines, Claude's compliance with instructions starts to degrade. Break complex rules into .claude/rules/ subdirectory files and use CLAUDE.md only for core instructions and an index
2. Make instructions specific and verifiable: "Use 2-space indentation" beats "Keep formatting clean." "Never use em dashes" beats "Write in a modern style"
3. Leave formatting to linters: Don't put code formatting rules in CLAUDE.md. Let tools like ESLint/Prettier handle that
4. Use WHAT/WHY/HOW structure: Each rule should explain what to do and why, giving Claude the context to make judgment calls in edge cases

This project (Shareuhack) uses CLAUDE.md to manage the entire content pipeline, from frontmatter formats and forbidden-word lists to agent role boundaries. Over 100 rules maintain consistency through this single file.

Quick start: Run /init in Claude Code, and it will scan your project and generate an initial CLAUDE.md.

Auto Memory: Patterns Claude Learns on Its Own

Auto Memory (~/.claude/projects/<project>/memory/MEMORY.md) is a memory file that Claude Code maintains automatically. Unlike CLAUDE.md, it doesn't contain your explicit instructions. Instead, it captures preferences and patterns that Claude learns from your interactions.

How it works:

• Claude observes how you modify its output, preferences you repeatedly emphasize, and your workflow habits
• It proactively writes these learnings into MEMORY.md
• At the start of the next session, the first 200 lines of MEMORY.md are automatically loaded

CLAUDE.md vs Auto Memory:

	CLAUDE.md	Auto Memory
Content	Rules you explicitly define	Preferences Claude learns from corrections
Author	You (manually written)	Claude (auto-generated)
Loading	Full file loaded	First 200 lines loaded
Best for	Fixed standards, prohibitions	Nuanced preferences, style patterns

The best practice is to treat them as complementary: CLAUDE.md holds "your requirements," while Auto Memory holds "what Claude has observed about you." If Auto Memory gets something wrong, you can edit MEMORY.md directly or tell Claude to correct it.

---

Layer 3: API Memory Tool (For App Builders)

If you're building AI applications with the Anthropic API, the Memory Tool lets you manage persistent cross-session memory within your own system, without relying on users to manually provide context.

When You Need It

Whenever your application needs to remember user information across conversations: a support bot that remembers customer preferences, a personal assistant that tracks long-term goals, or a learning app that monitors study progress.

Basic Operations

The API Memory Tool uses type memory_20250818 and supports six operations:

Operation	Purpose
view	Read current memory contents
create	Create a new memory file
str_replace	Replace a specific section in memory
insert	Insert new content at a specified position
delete	Remove specific content from memory
rename	Rename a memory file

{
  "type": "memory_20250818",
  "command": "str_replace",
  "path": "user_preferences.md",
  "old_str": "language: english",
  "new_str": "language: zh-TW"
}

Supported models: Opus 4.7/4.6/4.5, Sonnet 4.6/4.5, Haiku 4.5 (all current Claude model families are supported)

Cost: Approximately 2,500 tokens of overhead. The tool itself has no separate fee; you pay standard token rates.

Security Considerations

Since the Memory Tool operates on file paths, you must implement path traversal protection at the application layer:

• Validate that paths don't contain ../ or absolute paths
• Restrict the accessible directory scope
• Never let users directly control the path parameter

Managed Agents Built-in Memory and Dreaming (May 2026)

In May 2026, Anthropic shipped two significant memory updates for Managed Agents:

Built-in memory (public beta): Managed Agents now support workspace-scoped memory stores. Memories are saved as files that developers can export, manage via the API, and fully control. Every memory change creates an immutable version, providing an audit trail and point-in-time recovery.

Dreaming (research preview): Dreaming is a scheduled memory-curation process that lets agents review up to 100 past sessions, extract patterns, merge duplicates, remove stale entries, and write learnings as plain-text notes and structured "playbooks" for future sessions to reference. Critically, Dreaming does not modify the underlying model weights. It improves agent performance purely through memory curation.

Developers can choose to let Dreaming update memory automatically or review changes before they land. Dreaming currently supports Opus 4.7 and Sonnet 4.6, and requires access through claude.com/form/claude-managed-agents.

According to early case studies shared by Anthropic, legal AI company Harvey saw task completion rates increase roughly 6x after implementing Dreaming (self-reported).

---

Privacy and Security: Who Can See Your Memory Data?

Data Retention Policy

How Claude uses your memory data depends on your plan:

Plan	Default Training Setting	Can You Opt Out?
Free / Pro / Max	Training allowed by default (anonymized)	Yes
Incognito mode	Never used for training	N/A
Enterprise	Not used for training by default	N/A
API	Not used for training by default	N/A

How to opt out of training: Settings > Privacy > Turn off "Help improve Claude"

After opting out, your conversation and memory data is purged within 30 days. Data that has already entered the training pipeline won't be retroactively removed, but Anthropic states it will stop collecting new data from your account.

Memory Deletion and Reset

• Delete specific memories: Settings > Memory > delete individual items
• Reset all memory: Settings > Memory > Clear all (permanent, irreversible)
• After deleting a conversation: Related memories are automatically cleaned up within about 24 hours

Privacy Checklist

Before you start using Claude's memory features, confirm the following:

• Training settings in Settings > Privacy match your preferences
• For sensitive projects, consider using Project Memory for isolation
• For complete isolation, use Incognito mode (shortcut: Cmd + Shift + I)
• Periodically review Settings > Memory and clear outdated memories

---

Choose the Right Memory Layer for Your Role

The three layers aren't "advanced versions replacing the basic one." They're independent tools designed for different user roles:

• General Claude users: Enable Chat Memory and let Claude remember your preferences. If you have ChatGPT memories, use Memory Import to migrate them
• Claude Code developers: CLAUDE.md offers the highest ROI. Spending one hour writing a solid CLAUDE.md saves countless hours of repeated explanations. Let Auto Memory learn your finer preferences
• AI app builders: Use the API Memory Tool to give your applications genuine personalization capabilities; if you use Managed Agents, enable built-in memory and Dreaming to let agents continuously self-improve

The design philosophy behind Claude's memory system is simple: make AI adapt to you, not the other way around. Each of the three layers serves a different answer to "what do you want AI to remember?" The May 2026 addition of Managed Agents memory and Dreaming pushes this vision further into territory where agents proactively learn from experience. Find the layer that matches your role, set it up today, and within a few weeks you'll feel a noticeable difference.