// Delete specific observations or sessions from agentmemory. Use when user says "forget this", "delete memory", or wants to remove specific data for privacy.
Trace a file, function, or line back to the agent session that produced its current commit. Use when the user asks "why is this code here", "what was the agent doing when this changed", or wants context on a specific location in the codebase.
List recent git commits that are linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", or wants a list of commits with their session context.
Resume the most recent agent session for the current working directory. Use when the user says "where were we", "resume", "handoff", "pick up where I left off", or starts a session with no fresh context.
Summarize the last N agent sessions for the current project, grouped by date. Use when the user asks "recap", "what have we been doing", "this week", "today", or wants a rollup of recent work.
Search agentmemory for past observations, sessions, and learnings about a topic. Use when the user says "recall", "remember", "what did we do", or needs context from past sessions.
Explicitly save an insight, decision, or learning to agentmemory's long-term storage. Use when the user says "remember this", "save this", or wants to preserve knowledge for future sessions.
| name | forget |
| description | Delete specific observations or sessions from agentmemory. Use when user says "forget this", "delete memory", or wants to remove 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
IMPORTANT: This is a destructive operation. Always confirm with the user before deleting.
Steps:
First search for matching observations with the memory_smart_search MCP tool (provided by the agentmemory server this plugin wires up via .mcp.json). Use the user's input as the query with limit: 20.
Show the user what was found — session IDs, observation IDs, titles — and ask for explicit confirmation before deleting.
Once confirmed, call memory_governance_delete with:
memoryIds: [<id>, ...] — an array (or comma-separated string) of the memory IDs returned by the search in step 1reason: "<short reason>" — optional, defaults to "plugin skill request"If the user wants to drop an entire session's observations, collect every memory ID in that session from the search results and pass them all via memoryIds. The standalone MCP doesn't accept a bare sessionId argument — it deletes by memory ID only.
Confirm the deletion count back to the user.
Never delete without explicit user confirmation. If the MCP tools aren't available, the stdio MCP shim didn't start — tell the user to:
/plugin list in Claude Code and confirm agentmemory shows as enabled..mcp.json is only read on startup)./mcp to see whether the agentmemory MCP server is connected.