Forget

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

1. Search with memory_smart_search, the user's text as query, limit: 20. 2. Show what matched: session ids, memory ids, titles. Ask for explicit confirmation. Do not proceed on silence or a vague "sure, whatever". 3. On confirmation, call memory_governance_delete with memoryIds (array or comma-separated string) and optional reason (default plugin skill request). 4. 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. 5. Report the deletion count back.

Anti-patterns

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.

Checklist

• Matches were shown to the user before any delete.
• An explicit yes was received, not assumed.
• memoryIds holds real ids from the search, never a bare sessionId.
• Final message states the actual count deleted.

See also

• remember: the write side; forget is its undo.
• recall: find the exact memory id before deleting.

Troubleshooting

See ../_shared/TROUBLESHOOTING.md if memory_smart_search or memory_governance_delete is not available.

forget worked examples

1. Delete a leaked secret

User: "Forget that note where I pasted the API key."

Search:

memory_smart_search { "query": "api key", "limit": 20 }

Response:

{
  "results": [
    { "id": "abc12345", "sessionId": "7f3a9c21", "title": "Pasted staging API key",
      "narrative": "STAGING_KEY=sk-live-..." }
  ]
}

Present and gate:

Found 1 match:

- abc12345 (session 7f3a9c2) "Pasted staging API key"

>

Delete this memory? (yes/no)

After the user says yes:

memory_governance_delete { "memoryIds": ["abc12345"], "reason": "user privacy request" }

Response:

{ "deleted": 1 }

Present:

Deleted 1 memory (abc12345).

2. Drop a whole session's observations

User: "Delete everything from the throwaway spike session."

Search, identify the session, then collect every memory id in it:

memory_smart_search { "query": "spike prototype throwaway", "limit": 20 }

Response has 4 results all with sessionId: c98f1100. Show all four, get a yes, then pass every id:

memory_governance_delete {
  "memoryIds": ["m1", "m2", "m3", "m4"],
  "reason": "drop throwaway spike session"
}

Never send { "sessionId": "c98f1100" }; the MCP deletes by memory id only.

3. User declines

User: "Actually, on second thought, keep them."

Do not call delete. Confirm:

Understood, nothing deleted. The 4 memories from session c98f110 are intact.