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: [, ...] — an array (or comma-separated string) of the memory IDs returned by the search in step 1 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: Run /plugin list in Claude Code and confirm agentmemory shows as enabled. Restart Claude Code (the plugin's .mcp.json is only read on startup). Check /mcp to see whether the agentmemory MCP server is connected. Show more