forget

Deletes specific agentmemory observations by memory ID after explicit user confirmation.

3|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/Prismaibrowser/prismspace-web --skill forget-prismaibrowser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forget
Source: https://github.com/Prismaibrowser/prismspace-web/tree/main/.agents/skills/forget
Command: npx skills add https://github.com/Prismaibrowser/prismspace-web --skill forget-prismaibrowser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users need a safe way to permanently remove sensitive or unwanted data (like leaked API keys or throwaway session notes) from agentmemory without accidentally deleting the wrong records. ## Core Features & Use Cases - Search-then-delete workflow: Finds candidate memories with memory_smart_search, shows them to the user, and only deletes after an explicit yes. - Session-wide cleanup: Collects every memory ID in a session and deletes them all, since the MCP does not accept a bare sessionId. - Lesson deletion: Removes lessons separately via memory_lesson_delete, which memory_governance_delete does not touch. - Use Case: A user pastes a staging API key into a note and later asks to forget it; the skill locates the memory, confirms with the user, and deletes it by ID. ## Quick Start Ask the assistant to forget a specific memory by describing it, for example: forget the note where I pasted the API key.

Frequently Asked Questions about forget

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delete a specific memory from agentmemory?▼

Search for the memory with memory_smart_search using a descriptive query, review the returned memory IDs, then call memory_governance_delete with those IDs and a reason. Always confirm with the user before deleting because the operation is irreversible.

How to delete all memories from one session in agentmemory?▼

Search for memories in that session, collect every memory ID from the results, and pass them all to memory_governance_delete. The MCP does not accept a bare sessionId, so deletion must be done by individual memory IDs.

Can I delete a memory without confirming first?▼

No. The workflow requires showing the matched memories to the user and receiving an explicit yes before calling delete. Proceeding on silence or a vague response is an anti-pattern because deletion is destructive and irreversible.

Does memory_governance_delete remove lessons too?▼

No. Lessons are stored separately and are not touched by memory_governance_delete. To remove a lesson, call memory_lesson_delete with its lessonId instead.

Why did memory_governance_delete report zero deletions?▼

A deletion count of 0 means the supplied memory IDs did not exist in agentmemory. Verify the IDs came from a recent memory_smart_search result and report the actual count to the user rather than claiming a successful delete.