| name | forget |
| description | Delete specific observations or sessions from mempalace |
| argument-hint | [what to forget - session ID, file path, or search term] |
| user-invocable | true |
The user wants to remove data from mempalace: $ARGUMENTS
IMPORTANT: This is a destructive operation. Always confirm with the user before deleting.
Quick start
Search with memory_smart_search, show matches, confirm with user, then call memory_governance_delete.
Why
Remove stale, incorrect, or private data from the palace.
Workflow
- Call
memory_smart_search with the user's input as query, limit: 20.
- Show the user what was found (IDs, titles) and ask for explicit confirmation.
- On confirmation, call
memory_governance_delete with memoryIds: [<id>, ...].
- To drop a whole session, collect all memory IDs from the search results.
- Confirm the deletion count back to the user.
Anti-patterns
WRONG -- deleting without confirmation:
// Never auto-confirm. Always wait for explicit user approval.
RIGHT -- confirming first:
// "Found 3 observations. Delete all 3? [y/N]"
WRONG -- using bare sessionId:
// The MCP tool does not accept sessionId. Collect all memory IDs instead.
MCP tool unavailable
If MCP tools are unavailable:
- Run
/plugin list in Claude Code, confirm mempalace is enabled.
- Restart Claude Code (
.mcp.json is only read on startup).
- Check
/mcp to see if the mempalace MCP server is connected.
See _shared/TROUBLESHOOTING.md and EXAMPLES.md for more.