Know what loads at startup
Each file has a badge: always, startup, or conditional. Auto memory shows its MEMORY.md index and the notes it links to, which Claude reads only when it needs them.
CLAUDE.md files, rules, auto memory, agent memory, and the files they import, grouped by scope. Then let Claude find what is stale, false, or in conflict.
npx claude-code-memory-explorer --openThe 17 themes the app ships with, in light and dark. Pick one and the page follows.
The bar at the top shows how much text each scope adds, in characters and bytes. Click an@import to open the file it pulls in. Browsing changes nothing.
Each file has a badge: always, startup, or conditional. Auto memory shows its MEMORY.md index and the notes it links to, which Claude reads only when it needs them.
A rule with paths in its frontmatter loads only for matching files. The preview shows the paths, and the rule stays marked conditional in the tree.
The analysis runs claude -p in your project. The reviewers can read files but cannot edit them. Each run is saved, and new runs merge with the old ones.
Inside Claude Code Hub, the project you pick with Ctrl+Alt+P sets the project here too.
Claude reviews each file in parallel and checks its claims against your repository. Every finding names the files involved, says why it matters, and suggests a fix. Tick the findings you want fixed, copy them as one fix plan ordered by severity, and paste it into Claude Code.
Arrow keys move through the tree, E opens the file in your editor, and Shift+P switches the project. Press ? for the full list.
npx claude-code-memory-explorer --openRun it in your project. To look at another project, press Shift+P.
Optional. Click Analyze and pick the files and the model. It runs claude -p on your machine, so Claude Code must be logged in. Each run shows what it cost.