Memory Review

Curate the user's file-based agent memory: the long-form CLAUDE.md files plus the per-project auto-memory store, read through the Agent Monitor dashboard at http://localhost:4820.

Input

The user provides: $ARGUMENTS

This may be:

• empty, review the whole memory store across every project (default).
• a project slug (e.g. -Users-david-WebstormProjects-foo), restrict the review to that one project's auto-memory dir.
• "claude-md", review only the user/project CLAUDE.md files.

Data Sources

Endpoint	Returns
GET /api/cc-config/memory	{ items:[…] }. CLAUDE.md entries: { scope:"user"|"project", file, size, mtime, preview }. Auto-memory entries: { scope:"auto-memory", project, name, isIndex, file, size, mtime, frontmatter, preview }
GET /api/cc-config/file?path=<abs>	full body of one file: { ok, file, size, mtime, truncated, text }, use to read a fact in full before recommending an edit

Report Sections

1. CLAUDE.md overview

List the user and project CLAUDE.md entries with scope, size (KB), and last-modified (mtime). Note any that are truncated (over 256 KB), these are oversized and worth splitting into auto-memory facts.

2. Per-project auto-memory, grouped

Group scope: "auto-memory" items by project. For each project show the index (isIndex: true, typically MEMORY.md) first, then the per-fact files. For each fact show name, frontmatter.description if present, size, and mtime.

3. Index vs per-fact consistency

Within each project, compare the index (MEMORY.md) against the per-fact files present. Flag facts that exist on disk but are not referenced by the index, and index entries that point at files which no longer appear in /memory.