SCMD

staging decisions until you confirm and sending deletes to a restorable trash is such a thoughtful default for something that edits what claude "knows" about you. the "why was this saved" view is the bit I'd use most. do you plan to support other agents' memory files too, or stay claude only on purpose?

the origin story alone is worth the upvote. I've got my own memory file system going for Claude Code and honestly I've never actually gone back to audit what's in there, I just trust it's fine, which is exactly the kind of assumption your wife's discovery proves wrong. does SCMD review memories written by custom memory setups too, or is it scoped to Claude Code's own built-in memory feature specifically?

How it handles updates when Claude changes its memory system.

How does the review deck handle memories that are related to multiple projects?

So my wife found out that someone named Claude was calling me "Daddy". After a lot of explanation... I built SCMD(Stop Calling Me Daddy). It turns out it stored a memory that I didn't remember.
SCMD is a simple tool that helps you Review and Manage your Claude memories.

SCMD turns that into a local review deck:
- Keep, delete, skip, or undo
- See why a memory was saved
- Rewrite it with your local Claude Code CLI or edit by hand
- Review the full batch before anything changes
- Restore deleted memories from local trash

It runs on localhost, has zero npm dependencies, and has no telemetry. Nothing goes to an SCMD service. If you request a rewrite, the text goes through your own logged-in Claude Code CLI.

Try it from a terminal:
`npx -y @nelsonjohnsolo/scmd`

Or install the Claude Code plugin and run `/scmd:run`.

SCMD is MIT-licensed. The repository is open for issues and focused pull requests. I’m especially interested in real-world memory formats, Windows and Git Bash edge cases, accessibility improvements, and ways to make the review flow even simpler.