claude-code - 💡(How to fix) Fix [BUG] Claude Code deletes 160 session JSONL files (60,702 messages) — auto-memory saves nothing about months of work [3 comments, 3 participants]

Preflight Checklist

• I have searched existing issues — this is related to #48334, #46621, #41591, #41874, #39667, #41458 but adds forensic evidence and a new dimension (memory system failure)
• This is a single bug report
• I am using the latest version of Claude Code (VS Code extension, Windows 11)

What's Wrong?

Two compounding failures that together cause catastrophic knowledge loss:

Failure 1: Silent session file deletion

160 session JSONL files (60,702 messages, ~1GB) were deleted from disk. The sessions-index.json still exists with all 160 entries pointing to files that no longer exist.

Forensic evidence collected in-session:

sessions-index.json: 160 entries (Jan 27 – Mar 14, 2026)
JSONL files on disk: 0 of 160 remain
Today's sessions: 5 new files (Apr 15 only), ~32MB
Gap: Mar 15 – Apr 14 (one month) — never indexed, files also gone

The .claude/ directory is NOT under OneDrive sync — it's a plain local directory. The files were deleted by Claude Code itself (likely during an upgrade).

Failure 2: Auto-memory system retains nothing meaningful

Even if session files are treated as ephemeral, the auto-memory system (MEMORY.md + topic files) should preserve key decisions and relationships. It does not.

Experiment: We attempted to recover a significant session about "MATRIX" (MAITRIX/MemFlow integration — a multi-model AI hub partnership active since Feb 2026). Results:

The only reason this session was recoverable is because the user built their own archive system (Rootz Desktop V6 with SQLite + blockchain archival). Without that, months of collaborative thinking would be permanently lost.

The compounding effect

Claude creates an illusion of continuity — the user experiences a persistent collaborator ("I've been working with Claude for months") while Claude experiences each session as day one. When session files disappear AND the memory system saves nothing, the user discovers too late that the AI retained zero trace of their shared work.

What Should Happen?

1. Session JSONL files must never be silently deleted — especially not during upgrades. If cleanup is needed, archive first or require explicit user consent.
2. sessions-index.json should not be orphaned — if files are deleted, the index should reflect reality.
3. Auto-memory should be far more aggressive — key decisions, relationships, project names, partner names, and architectural choices should be saved automatically, not left to Claude's discretion.
4. Users should be warned when session data is about to be or has been deleted.
5. MCP servers should be able to provide memory backends — see #48465, #47023

Steps to Reproduce

1. Use Claude Code VS Code extension on Windows for 2+ months
2. Accumulate 160+ sessions with significant collaborative work
3. Allow Claude Code to auto-update
4. Check ~/.claude/projects/{slug}/ — JSONL files are gone
5. Check sessions-index.json — still references 160 entries to missing files
6. Ask Claude "what do you know about [topic from a deleted session]" — answer: nothing

Environment

• Platform: Windows 11 Pro 10.0.26200
• Claude Code: VS Code extension (latest)
• Model: Claude Opus 4.6
• Session count (indexed): 160
• Session count (surviving): 0
• Messages lost: 60,702
• Date range of lost sessions: Jan 27 – ~Apr 14, 2026
• Memory files: 37 (none reference the lost MATRIX session)

Related Issues

• #48334 — Desktop app update deletes session history
• #46621 — Critical: silently deletes conversation history
• #41591 — Auto-update deletes session .jsonl files
• #41458 — cleanupPeriodDays ignored, 490 sessions deleted
• #40877 — Active sessions missing + memory persistence unreliable
• #48465 — Allow MCP servers to replace auto memory backend
• #47023 — Expose compact/session lifecycle hooks for external memory
• #46283 — Claude Code ignored MEMORY.md warning

Additional Context

This is being documented as part of a research paper on AI memory loss: "The Illusion of Continuity in AI Agent Relationships." The forensic evidence, experiment methodology, and recovery attempts are recorded in docs/RESEARCH-ai-memory-loss.md.

The user quote that captures the problem: "I can not believe how flippant Claude is with memory. There is months of work, organized thinking, and poof — the assumption is you remember, which you don't."