Memory files are local-only — no cloud sync, misleading for users coming from Claude.ai

Problem

Claude Code's memory system stores files locally on disk (~/.claude/). There is no cloud sync tied to the user's account.

Users coming from Claude.ai (browser) reasonably expect memory/notes to be account-based and cloud-synced, as they are in Claude.ai projects. This is not the case in Claude Code, and this distinction is not clearly communicated.

Real-world impact

A user was working with Claude Code on a hardware problem. Claude Code saved memory notes to disk. The user needed to reinstall Linux — a step Claude Code itself recommended. Before reinstalling, the user explicitly asked Claude to save notes so they could resume after the reinstall. Claude wrote the memory files without warning the user that a Linux reinstall would permanently destroy them.

After the reinstall, all notes were gone. The user lost their entire context.

What should happen

Either:

1. Memory should be synced to the cloud, tied to the user's Claude account — consistent with Claude.ai behavior, OR
2. Claude Code should prominently warn users that memory files are local-only and will not survive a disk wipe or OS reinstall, especially when it is about to recommend such an action

Why this matters

The inconsistency between Claude.ai (cloud) and Claude Code (local) is a trap for users. They trust the system to persist their work. When it silently doesn't, they lose time, context, and trust.