memman
v0.1.0
Published
Local web UI to visualize, edit, create and delete Claude Code memory files.
Maintainers
Readme
meman
A tiny local web UI to visualize, edit, create, and delete the memory files
that Claude Code keeps under ~/.claude/projects/<project>/memory/.
Each memory is a markdown file (--- frontmatter + body). This tool renders them
as structured cards grouped by type (feedback / project / reference / user),
lets you edit the fields in place, and keeps the hand-curated MEMORY.md index in
sync when you delete a memory.
Run
cd memory-manager
npm install
npm start
# → http://localhost:4785The memory directory is auto-detected from your current working directory using Claude Code's project-slug scheme. Override it explicitly when needed:
node server.js --dir ~/.claude/projects/-home-me-myproject/memory
node server.js --dir <path> --port 5000
# env vars also work: MEMORY_DIR=... PORT=... npm startIf several project memory dirs exist and none matches the cwd, the tool prints the
candidates and asks you to pass --dir.
Later: run on the fly
package.json declares a bin, so once published:
npx meman --dir <path>What it does
- Edit — change name / description / type / body per card. Hidden frontmatter
(
node_type,originSessionId) is preserved untouched, and flat vs. nested frontmatter files round-trip in their original format. - Create — "+ New memory" writes a properly-formatted file (nested format).
Note: it does not auto-add a
MEMORY.mdindex line — that index is curated by hand, so add the pointer yourself if you want the memory recalled. - Delete — moves the file to
memory-manager/.trash/(soft delete) and removes its reference fromMEMORY.md: a bullet whose only link is that file is dropped; a bullet that bundles several links keeps the others.
Safety
- All file access is confined to the resolved memory dir; filenames are validated
(
^[A-Za-z0-9_-]+\.md$) and path traversal is rejected. - Deletes are soft (recoverable from
.trash/). MEMORY.mdis only ever touched on delete, never on edit/create.
