Find and delete selected memories stored in agentmemory after showing the matches and receiving explicit confirmation. It checks deletion results and distinguishes stored memories from lessons, observations, and complete session records.
Delete selected durable memories from agentmemory after showing them and getting explicit confirmation. Use when the user says "forget this", "delete memory", "remove that note", or wants to scrub specific data for privacy.
Review the instructions the agent will receive before you install.
The user wants to remove data from agentmemory: $ARGUMENTS
memory_smart_search { "query": "old api key in config", "targetLayer": "memory", "limit": 20 }
Show the matches, get a yes, then:
memory_governance_delete { "memoryIds": "abc12345,def67890", "reason": "user privacy request" }
Expected output:
Found 2 matching memories. Confirmed. Deleted 2 memories.
This is destructive and irreversible. Show exactly what will be deleted and get an explicit yes before calling delete. Delete by memory ID, never a bare session.
memory_smart_search, the user's text as query,
targetLayer: "memory", limit: 20, and the requested project/agent scope.
These are selected relevance matches, not an exhaustive inventory.memory_governance_delete with memoryIds as a
comma-separated string and optional reason (default plugin skill request).sessionId.memory_lesson_delete and its
lessonId; memory_governance_delete does not touch lessons.deleted, notFound, and failed in the response. Report actual
deletions and unresolved IDs separately. Recheck the selected IDs before
retrying a failed request; an interrupted response may hide a completed write.WRONG: search returns matches, you immediately call memory_governance_delete
without showing them or waiting for a yes.
RIGHT: list the matches, ask "Delete these 2? (yes/no)", and only delete after an explicit yes.
memoryIds holds real ids from the search, never a bare sessionId.remember: the write side; forget is its undo.recall: find the exact memory id before deleting.See TROUBLESHOOTING.md if memory_smart_search or memory_governance_delete is not available.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Connect agentmemory to coding agents such as Claude Code and Codex while preserving existing server settings. It guides configuration, host restarts, and checks that memory tools are available and can save and retrieve information.
Explain how agentmemory stores and retrieves coding agents’ memories, including its engine, search methods, memory lifecycle, ports, and web viewer. Useful for understanding the system or planning extensions to its functions.
Set up and troubleshoot a local agentmemory server by checking MCP connections, authentication, ports, and environment settings. Understand which optional memory features require additional configuration, model downloads, or token usage before enabling them.
Understand how agentmemory automatically records tool activity, prompts, and session boundaries through hooks, actions triggered by session events. Use it to check integration setup, investigate missing records, and distinguish capture from optional summaries and context injection.
Helps agents choose the right agentmemory tool through MCP, a protocol for connecting agents to tools. It explains tool roles and points to parameter references for saving, retrieving, organizing, and maintaining stored knowledge.
Guides HTTP integration with the agentmemory server for saving and searching knowledge. It explains authentication, request conventions, and endpoint references, including how to connect systems that do not support MCP, the agent tool connection protocol.