com um clique
remember
// 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.
// 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.
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.
Delete specific observations or sessions from agentmemory. Use when user says "forget this", "delete memory", or wants to remove specific data for privacy.
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.
| name | remember |
| description | 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. |
| argument-hint | [what to remember] |
| user-invocable | true |
The user wants to save this to long-term memory: $ARGUMENTS
Use the memory_save MCP tool (provided by the agentmemory server that this plugin wires up automatically via .mcp.json) to persist it.
Steps:
concepts (lowercased keyword phrases) that capture what the memory is about. Prefer specific terms over generic ones ("jwt-refresh-rotation" beats "auth").files — absolute or repo-relative paths the memory references.memory_save with the fields:
content — the full text to remember (preserve the user's phrasing as much as possible)concepts — the extracted concept listfiles — the extracted file list (empty array if none apply)If memory_save isn'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.