Claude Memory Navigator FAQs

Question 1

How do I use imports in my Claude memory files?

Accepted Answer

You can use the @ symbol followed by a relative or absolute file path (e.g., @./docs/architecture.md) to include other files. Claude supports up to 5 levels of recursive resolution.

Question 2

When should I move rules from CLAUDE.md to the rules folder?

Accepted Answer

You should migrate when your CLAUDE.md exceeds 300 lines, when sections become bloated, or when rules need to be applied selectively to specific file paths using the rules folder functionality.

Question 3

What is the priority order of Claude Code memory sources?

Accepted Answer

The system follows a specific hierarchy from highest to lowest: Enterprise Policy, Project Rules (.claude/rules/*.md), Project Memory (CLAUDE.md), User Memory (~/.claude/CLAUDE.md), and finally Local Memory (CLAUDE.local.md).

Question 4

How can I check which memory files Claude has currently loaded?

Accepted Answer

You can use the /memory command within the Claude Code interface to display a list of all memory sources currently active in your session.

Question 5

What is the difference between User Memory and Local Memory?

Accepted Answer

User Memory (~/.claude/CLAUDE.md) contains personal settings that apply to all your projects, while Local Memory (CLAUDE.local.md) contains settings specific to one project that are typically excluded from Git.

Claude Memory Navigator

About

Key Features

Use Cases

Claude Memory Navigator

About

Key Features

Use Cases