crux-forget

Prompt file imported from zotoio/CRUX-Compress (.cursor/commands/crux-forget.md). Fill in {{arguments}} before use. Copyright stays with the author.

crux-forget

Remove memories from the CRUX memory corpus.

Repository: github.com/zotoio/CRUX-Compress

Usage

/crux-forget <memory-id>           - Forget a specific memory by its short hash ID
/crux-forget <slug>                - Forget a memory by slug
/crux-forget <file-path>           - Forget a memory by file path
/crux-forget "search query"        - Search memories and select which to forget
/crux-forget                       - List all memories for selection

Instructions

This command uses Pattern B (work first, then escalate) — the subagent must search and resolve memory matches before the user can choose which to delete. The parent agent (you) orchestrates the workflow: spawn a subagent to resolve matches, confirm deletion with the user via AskQuestion, then resume the subagent to perform confirmed deletions. The subagent never calls AskQuestion directly.

Argument Handling

• Memory ID(s) (7-char hex hash, e.g. a1b2c3d): Pass {{arguments}} to the subagent to resolve.
• Slug(s) (e.g. validate-checksums-before-overwrite): Pass {{arguments}} to the subagent to resolve.
• File path(s) (e.g. memories/learning/foo.memory.md): Pass {{arguments}} to the subagent to resolve.
• Quoted text (e.g. "performance optimization"): Pass {{arguments}} to the subagent as a search query.
• No arguments: The subagent loads the memory index and returns all memories for selection.

What Happens

Phase 1 — Subagent resolves matches:

1. Spawn a crux-cursor-memory-manager subagent in Forget mode, passing {{arguments}}
2. The subagent resolves the input to matching memory files and returns them with ID, title, type, strength, and file path
3. If the subagent returns needs_user_input with the resolved matches, proceed to Phase 2

Phase 2 — Parent confirms deletion with user:

4. Display matched memories to the user with their details
5. Use the AskQuestion tool to confirm which memories to delete — present each memory as a multi-select option. Always confirm before deletion — this operation is destructive and irreversible.

Phase 3 — Resume subagent with confirmed list:

6. Resume the subagent with the list of confirmed memory IDs/paths to delete
7. The subagent deletes each confirmed memory via crux-skill-memory-crud Delete operation:
   • Removes the memory file (.memory.md or .memory.crux.md)
   • Removes the corresponding reference tracker ({trackingDir}/{slug}.refs.yml) if it exists
8. The subagent rebuilds the memory index via crux-skill-memory-index
9. Display the subagent's report: count, types, and IDs of removed memories

Related

• crux-cursor-memory-manager agent — The specialist that manages the memory lifecycle
• crux-skill-memory-crud skill — Delete operation that handles memory file and tracker removal
• /crux-dream — Extract and create memories from completed work
• /crux-recall — View and query memories
• /crux-remember — Create ad-hoc memories outside of spec workflows
• /crux-meditate — Recursive memory-informed exploration