memory · hoangsonww — Claude Code command: what it does, how to install
Lists file-based memory stores and CLAUDE.md files grouped by project via the Agent Monitor dashboard.
MIT ★ 1,198 updated 2026-10-23
/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor
/plugin install ccam-config@claude-code-agent-monitor-pluginsWhat memory does
The command queries the Agent Monitor Config Explorer API at http://localhost:4820/api/cc-config/memory. It checks user-level and project-level CLAUDE.md files, displaying their sizes in kilobytes and modification timestamps while flagging truncated entries.
It then organizes auto-memory notes by project slug, displaying index files such as MEMORY.md before individual fact files with frontmatter descriptions. Supplying an optional argument filters the project list. The command requires an active dashboard on port 4820; if unreachable, start it using npm start from the repository root.
What it helps with
- inspect user and project CLAUDE.md file sizes
- filter auto-memory notes by project name
- review modification dates of project MEMORY.md index files
Example prompts for the agent
- /memory
- /memory backend-service
- List all auto-memory records using
/memory
How to install memory
1Plugin marketplace
/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor/plugin install ccam-config@claude-code-agent-monitor-plugins2Manually: put the files in place
.claude/commands/ccam-config-memory.mdThe built-in /memory overrides a file with the same name, so the file is renamed. Call it with /ccam-config-memory. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/memory.mdCall it with /prompts:memory. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/memory.prompt.mdManually: put the files in place
.gemini/commands/memory.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about memory
How to install memory in Claude Code?
Run /plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor first, followed by /plugin install ccam-config@claude-code-agent-monitor-plugins.
What does the memory command do?
It fetches data from http://localhost:4820 and prints a structured view of CLAUDE.md configs and project-specific auto-memory files.
Why does the memory command report an unreachable dashboard?
The tool reads data directly from the local API on port 4820. Start the server by executing npm start from the repository root.
Source text
memory.md · MIT
---
description: List the file-based memory store grouped by project (auto-memory) plus the CLAUDE.md files.
argument-hint: "[project-filter]"
---
List the user's file-based memory store from the Agent Monitor Config Explorer
at `http://localhost:4820`. If **$ARGUMENTS** is given, treat it as a
project-slug filter and show only matching auto-memory groups.
```bash
curl -s http://localhost:4820/api/cc-config/memory
```
The response is `{ items: [...] }`. Two kinds of entry:
- **CLAUDE.md** — `{ scope:"user"|"project", file, size, mtime, preview }`.
- **Auto-memory facts** — `{ scope:"auto-memory", project, name, isIndex, file,
size, mtime, frontmatter, preview }`.
Print in two parts:
1. **CLAUDE.md** — one line per entry: `scope`, `size` (KB), last-modified.
Flag any with `truncated: true` as oversized.
2. **Auto-memory, grouped by `project`** — for each project (filtered by
`$ARGUMENTS` if provided), list the index file (`isIndex: true`, usually
`MEMORY.md`) first, then each per-fact file with `name`,
`frontmatter.description` (or start of `preview`), `size` (KB), and `mtime`.
```
Memory store
CLAUDE.md
user ..... 8.2 KB modified 3d ago
project .. 1.1 KB modified 1h ago
Project: -Users-david-WebstormProjects-foo (4 files)
MEMORY.md (index) ......... 0.6 KB
feature_x_decision.md ..... 0.3 KB — "why we chose X over Y"
api_quirk.md .............. 0.2 KB — "endpoint Z returns 200 on error"
```
Cite only fields the API returned — never invent facts, names, or sizes. Note
that auto-memory files are editable via `PUT`/`DELETE /api/cc-config/file`
(a backup is taken automatically) but this command is read-only. If the
dashboard is unreachable, say so and tell the user to start it with `npm start`
from the repo root.
© Son Nguyen · MIT · hoangsonww/Claude-Code-Agent-Monitor
Similar slash commands
All slash commands for Agent setup: memory, context, orchestration →memory by other authors comes first.