forget

rohitg00/agentmemory

Delete specific memories from agentmemory with explicit user confirmation.

What is forget?

Removes selected observations from agentmemory after showing matches and getting explicit yes/no confirmation. Use when the user requests deletion of notes, memories, or sensitive data for privacy reasons.

Search agentmemory for matching observations using natural language queries
Display matched memories with session IDs and titles before deletion
Require explicit user confirmation before any irreversible deletion
Delete by memory ID to avoid accidental session-wide removal
Handle lessons separately using dedicated lesson deletion
Report actual deletion count to confirm success

How to install forget

npx skills add https://github.com/rohitg00/agentmemory --skill forget

Claude Code

Cursor

Windsurf

Cline

How to use forget

1.Call memory_smart_search with the user's query and limit of 20 to find matching memories
2.Display the matched memories showing session IDs, memory IDs, and titles
3.Ask the user for explicit yes/no confirmation before proceeding
4.On confirmation, call memory_governance_delete with the memory IDs and optional reason
5.Report the actual count of deleted memories back to the user

Use cases

Good for

User wants to remove an old API key or credential from memory
Delete sensitive personal information or notes for privacy
Remove outdated session data or obsolete observations
Scrub specific memories matching a search term or description
Drop entire sessions by collecting and deleting all their memory IDs

Who it's for

Users managing sensitive data in agentmemory
Anyone needing privacy control over stored observations
Developers cleaning up test or temporary memories
Teams handling compliance or data retention policies

forget FAQ

What happens if I delete a memory by mistake?

Deletion is irreversible. The skill requires explicit confirmation before any delete, and shows you exactly what will be removed first.

Can I delete an entire session at once?

Yes, but you must collect every memory ID in that session from search results and pass them all to memory_governance_delete; the API does not accept a bare sessionId.

Are lessons deleted with memory_governance_delete?

No. Lessons are separate and must be deleted using memory_lesson_delete with the lessonId.

What if the search returns no matches?

The skill will report 0 matches. If you then call delete with IDs that don't exist, it returns a count of 0 instead of claiming a deletion.

Do I need to show the user what will be deleted?

Yes. Always list the matches and get explicit confirmation before calling delete. Proceeding on silence or vague approval is an anti-pattern.

Full instructions (SKILL.md)

Source of truth, from rohitg00/agentmemory.

name: forget description: Delete specific observations 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. argument-hint: "[what to forget - session ID, file path, or search term]" user-invocable: true

The user wants to remove data from agentmemory: $ARGUMENTS

Quick start

memory_smart_search { "query": "old api key in config", "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.

Why

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.

Workflow

Search with memory_smart_search, the user's text as query, limit: 20.
Show what matched: session ids, memory ids, titles. Ask for explicit confirmation. Do not proceed on silence or a vague "sure, whatever".
On confirmation, call memory_governance_delete with memoryIds (array or comma-separated string) and optional reason (default plugin skill request).
To drop a whole session, collect every memory id in that session from the search results and pass them all. The MCP does not accept a bare sessionId.
Lessons are separate: delete one with memory_lesson_delete and its lessonId; memory_governance_delete does not touch lessons.
Report the deletion count back. A count of 0 means the ids did not exist; say so instead of claiming a delete.