Menú
Delete specific observations or sessions from mempalace
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Diagnose mempalace setup (config, palace path, MCP, FTS/index health)
List or inspect people/project entities tracked in the mempalace graph
Mine a project directory into the mempalace corpus (drawers, rooms, wings)
Hybrid search over the mempalace corpus (BM25 + vectors + optional graph)
Show mempalace palace status (drawers, wings, rooms, health)
Trace a file, function, or line back to the agent session that produced its current commit
| 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.
Search with memory_smart_search, show matches, confirm with user, then call memory_governance_delete.
Remove stale, incorrect, or private data from the palace.
memory_smart_search with the user's input as query, limit: 20.memory_governance_delete with memoryIds: [<id>, ...].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.
If MCP tools are unavailable:
/plugin list in Claude Code, confirm mempalace is enabled..mcp.json is only read on startup)./mcp to see if the mempalace MCP server is connected.See
_shared/TROUBLESHOOTING.mdandEXAMPLES.mdfor more.