We Investigated Why Claude’s Memory Fails. Here’s What We Learned

Memory is arguably the most fundamental capability for a useful agent. Without it: The agent can't adapt to a user's preferences over time It repeats the same mistakes across sessions The user has to re-prompt the same rules every conversation ("always use strict typing", "never mock the database in tests", "our auth token expiry is 900s") This isn't a minor UX annoyance — it's the difference between an agent that gets better the more you use it and one that resets to zero every session. The problem with Claude's native memory Claude Code gives you two options: CLAUDE.md — you write it, you maintain it. Rules the agent should follow, project context, conventions. Fully manual. MEMORY.md — Claude maintains it automatically, appending notes during sessions. No manual work. MEMORY.md sounds like it solves the problem. In practice it has three hard constraints: Constraint What it means Per-repo scope Global preferences (code style, team conventions) have to be duplicated into every project