SCMD

Product Introduction

1. Definition: SCMD (Stop Calling Me Daddy) is an open-source, local-first memory management and review tool specifically designed for Claude Code, an AI coding assistant. It operates as a self-hosted web application that audits and curates the persistent memory files Claude Code automatically generates and stores on a user's local machine.
2. Core Value Proposition: SCMD exists to provide developers with transparent control and governance over AI assistant memory. It solves the problem of opaque, accumulating, and potentially stale AI memories by offering a local review deck for Claude Code persistent memories, enabling users to inspect, filter, and decide the fate of each memory before any changes are permanently applied.

Main Features

1. Local Memory Review Deck: SCMD launches a local web server (bound to 127.0.0.1) that presents all discovered Claude Code memories as interactive cards. It reads from the default ~/.claude/projects directory, displaying memories chronologically with full project context and memory text. The interface provides live updates and requires no external dependencies at runtime.
2. Staged Decision Workflow: All user actions—Keep, Delete, Skip, Undo, or Rewrite—are held in a staged state within the browser session. No files are altered until the user explicitly confirms the batch via an "Apply" action. This non-destructive approach prevents accidental data loss and allows for comprehensive review before commitment.
3. Advanced Memory Inspection & Management:
   • Inspection: Users can search memory text, filter by project or memory type, and view the originating session message that triggered a memory's creation (when traceable from .jsonl transcripts).
   • Editing: Memories can be rewritten via integration with the local Claude Code CLI (sending instructions to the user's logged-in account) or edited manually. All edits remain staged until final application.
   • Trash System: Deleted memories are moved to a restorable trash directory (~/.scmd/trash/) with metadata, allowing for safe recovery or permanent purging in separate, explicit operations.

Problems Solved

1. Pain Point: Lack of visibility and control over AI-generated persistent memory. Claude Code silently writes memories that can become outdated, irrelevant, or contain unintended information, which are then recalled in future sessions without user oversight.
2. Target Audience: Developers and technical professionals who use Claude Code extensively, particularly those working on multiple projects, in sensitive domains, or who are concerned about AI context bloat, privacy, and the accuracy of information retained by their coding assistant.
3. Use Cases:
   • Periodic AI Memory Hygiene: Conducting regular audits to remove stale project context, outdated code patterns, or incorrect information from Claude's memory.
   • Pre-Project Cleanup: Reviewing and clearing memories from a finished project before starting a new, unrelated one to prevent context contamination.
   • Privacy & Security Review: Inspecting exactly what information Claude Code has stored locally, especially after working with proprietary code or sensitive data.
   • Debugging AI Behavior: Using the "why was this saved?" origin feature to understand what specific interaction prompted a particular memory, which is useful for refining prompts and instructions.

Unique Advantages

1. Differentiation: Unlike built-in AI memory settings which may only offer global on/off toggles, SCMD provides granular, file-by-file control. Compared to manual file system editing, it offers a safe, structured, and informative interface with a non-destructive workflow, conflict detection (refuses to overwrite a changed memory), and integrated rewriting tools.
2. Key Innovation: Its privacy-first, local-only architecture with a staged approval model is the core innovation. SCMD enforces a clear separation between review and execution, operates with zero telemetry, requires no cloud service, and has zero npm dependencies at runtime, ensuring all data and decisions remain entirely on the user's machine.

Frequently Asked Questions (FAQ)

1. Is SCMD a cloud service or does it send my data anywhere? No, SCMD is a local-only, self-hosted tool with no telemetry. The review server runs on your local machine (127.0.0.1), and all memory data is processed in your browser. API calls are secured with a per-launch token. Network use is limited to the initial package fetch via npx or the Claude Code CLI if you explicitly choose the rewrite feature.
2. How does SCMD handle memory rewrites and editing? SCMD offers two paths: you can instruct it to rewrite a memory via your local Claude Code CLI (which uses your logged-in account), or you can edit the Markdown text directly within the review interface. Crucially, all rewritten or edited content remains staged in the browser until you confirm the entire batch, preventing immediate and potentially unwanted changes.
3. What happens if I accidentally delete a memory I needed? SCMD implements a restorable trash system. When you confirm a deletion, the memory file is moved to a dedicated ~/.scmd/trash/ directory with metadata intact. You can later browse this trash and restore memories to their original location, or permanently purge them in a separate operation.
4. Can I use SCMD with a custom Claude Code directory structure? Yes. If you use a custom CLAUDE_CONFIG_DIR environment variable or a non-standard auto-memory root, you can pass the --root <directory> argument to both the /scmd:run plugin command and the terminal npx command to point SCMD to the correct location.
5. What are the technical requirements to run SCMD? You need Node.js 18 or newer (which includes npm/npx). The primary launch method is via the Claude Code plugin marketplace. For terminal use, Windows users require Git Bash for full compatibility with the provided shell commands under the current best-effort support.