forget

Use it when:: You want a saved memory gone: "forget this", one saved by mistake, or data you want scrubbed for privacy.
It does:: Searches saved memories, shows the matches with secrets redacted, and deletes them by id only after an explicit yes.
You get:: The count actually deleted, with ids not found or failed listed separately.
Can't:: Erase captured observations or whole sessions; a lesson is deleted with its own call.
Needs:: agentmemory's memory server running, with its MCP tools connected to your agent.

Skill 4 of 8 in the agentmemory bundle, after remember and before session-history.

TL;DR

Part of agentmemory, a memory server that keeps what coding agents learn across sessions. forget is the undo for remember, and deletion can't be reversed, so it confirms first. The agent searches saved memories for what you described, within the project or agent you name; the results are relevance matches, not an inventory of everything stored. It lists the matching memory ids, titles and scope with secret values redacted and asks for an explicit yes: silence or a vague "sure, whatever" doesn't count. Then it deletes those ids, with a reason you can give. It explains up front that this removes selected memories only, not captured observations or a whole session, and lessons are removed with a separate delete. Afterwards it reports actual deletions apart from ids not found or failed, and checks the ids again before retrying a failed request.

Summarizes the skill at f0f7378.

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

skills.sh page Source on GitHub All skills from rohitg00/agentmemory

Total Downloads: 14,400 on skills.sh, Nov 9, 2026
Repo stars: 30,216 rohitg00/agentmemory
First seen: Apr 7, 2026 on skills.sh

Weekly Downloads

262

-34% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	398
Sep 28	375
Oct 5	348
Oct 12	320
Oct 19	333
Oct 26	318
Nov 2	307
Nov 9	262

Category	category:agents category:software-engineering Build agents, orchestrate workers and give agents memory. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:tool Operates a CLI, API, app or bundled script to get something done.
Effect	effect:local Its own steps create or change files, git state or local tools.
Needs	needs:mcp Needs an MCP server connected.
Publisher	by:official A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics	memory privacy
Stack	stack:agentmemory

SKILL.md

From rohitg00/agentmemory at f0f7378. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: forget
description: 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.
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", "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.

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, targetLayer: "memory", limit: 20, and the requested project/agent scope. These are selected relevance matches, not an exhaustive inventory.
Show what matched: memory ids, titles, and scope. Redact secret values. Ask for explicit confirmation. Do not proceed on silence or a vague "sure, whatever".
On confirmation, call memory_governance_delete with memoryIds as a comma-separated string and optional reason (default plugin skill request).
Observation or whole-session erasure is not supported by this operation. Explain that limit before proceeding; never label selected memory deletion as a complete session wipe. Do not pass observation IDs or a sessionId.
Lessons are separate: delete one with memory_lesson_delete and its lessonId; memory_governance_delete does not touch lessons.
Check 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.

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.

Troubleshooting

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