// 7 tips tagged "memory"
Claude Code can remember things between sessions — use /memory to save project decisions, your preferences, and important context so you don't have to re-explain the same things every time you start a new conversation.
Split your dev docs into three focused files (plan, context, tasks) so Claude can re-orient instantly after a context reset without wading through a single bloated plan.md.
Set autoMemoryEnabled to false in settings.json to stop Claude Code silently writing memory files, without losing any context already captured.
Claude Code can automatically save notes about your project across sessions — build commands, debugging insights, and your corrections — without you writing a single line of CLAUDE.md.
Pass custom instructions to /compact so Claude preserves test output, code changes, and other context that matters to your workflow.
Start any message with # to instantly save a note to Claude Code's persistent memory — without breaking your flow to run a separate command.
Every time you correct Claude or agree on a preference, capture it in CLAUDE.md — it becomes the persistent memory that carries across every future session.