@agentmemory/agentmemory 0.8.8 → 0.8.10

package/plugin/skills/forget/SKILL.md

@@ -10,23 +10,17 @@ The user wants to remove data from agentmemory: $ARGUMENTS
 **IMPORTANT**: This is a destructive operation. Always confirm with the user before deleting.
 
 Steps:
-1. First, search for matching observations:
-   ```bash
-   curl -s -H "Content-Type: application/json" \
-     -H "Authorization: Bearer ${AGENTMEMORY_SECRET:-}" \
-     -X POST "http://${AGENTMEMORY_URL:-localhost:3111}/agentmemory/search" \
-     -d '{"query": "<SEARCH_TERM>", "limit": 20}'
-   ```
 
-2. Show the user what was found and ask for confirmation
-3. If confirmed, delete via:
-   ```bash
-   curl -s -H "Content-Type: application/json" \
-     -H "Authorization: Bearer ${AGENTMEMORY_SECRET:-}" \
-     -X POST "http://${AGENTMEMORY_URL:-localhost:3111}/agentmemory/forget" \
-     -d '{"sessionId": "<ID>"}' # or {"observationIds": ["id1", "id2"]}
-   ```
+1. 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`.
+2. Show the user what was found — session IDs, observation IDs, titles — and ask for explicit confirmation before deleting.
+3. 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 1
+   - `reason: "<short reason>"` — optional, defaults to `"plugin skill request"`
 
-4. Confirm deletion to the user
+   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.
+4. Confirm the deletion count back to the user.
 
-Never delete without explicit user confirmation.
+**Never delete without explicit user confirmation.** If the MCP tools aren't available, the stdio MCP shim didn't start — tell the user to:
+1. Run `/plugin list` in Claude Code and confirm `agentmemory` shows as enabled.
+2. Restart Claude Code (the plugin's `.mcp.json` is only read on startup).
+3. Check `/mcp` to see whether the `agentmemory` MCP server is connected.

package/plugin/skills/recall/SKILL.md

@@ -5,14 +5,17 @@ argument-hint: "[search query]"
 user-invocable: true
 ---
 
-Search agentmemory for observations matching: $ARGUMENTS
+The user wants to recall past context about: $ARGUMENTS
 
-!`QUERY=$(echo "$ARGUMENTS" | sed 's/\\/\\\\/g; s/"/\\"/g') && curl -s -H "Content-Type: application/json" -H "Authorization: Bearer ${AGENTMEMORY_SECRET:-}" -X POST http://${AGENTMEMORY_URL:-localhost:3111}/agentmemory/search -d "{\"query\": \"${QUERY}\", \"limit\": 10}" 2>/dev/null || echo '{"results":[]}'`
+Use the `memory_smart_search` MCP tool (provided by the agentmemory server that this plugin wires up automatically via `.mcp.json`) with the user's query as the `query` argument and `limit: 10`. The tool runs hybrid BM25 + vector + graph-expanded search over captured observations and returns ranked results.
 
-Present the search results to the user in a readable format:
+Present the returned results to the user in a readable format:
 - Group by session
-- Show observation type, title, and narrative
+- For each observation show its type, title, and narrative
 - Highlight the most important observations (importance >= 7)
-- If no results found, suggest alternative search terms
+- If no results come back, suggest 2-3 alternative search terms the user could try
 
-Do NOT make up or hallucinate results. Only present what was returned from the search.
+**Do NOT make up or hallucinate observations.** Only present what the MCP tool actually returned. If `memory_smart_search` isn't available, the stdio MCP shim didn't start — tell the user to:
+1. Run `/plugin list` in Claude Code and confirm `agentmemory` shows as enabled.
+2. Restart Claude Code (the plugin's `.mcp.json` is only read on startup).
+3. Check `/mcp` to see whether the `agentmemory` MCP server is connected.

package/plugin/skills/remember/SKILL.md

@@ -7,19 +7,19 @@ user-invocable: true
 
 The user wants to save this to long-term memory: $ARGUMENTS
 
-To save this, make a POST request using the Bash tool:
-
-```bash
-curl -s -H "Content-Type: application/json" \
-  -H "Authorization: Bearer ${AGENTMEMORY_SECRET:-}" \
-  -X POST "http://${AGENTMEMORY_URL:-localhost:3111}/agentmemory/remember" \
-  -d '{"content": "<ESCAPED_CONTENT>", "concepts": [<CONCEPTS>], "files": [<FILES>]}'
-```
+Use the `memory_save` MCP tool (provided by the agentmemory server that this plugin wires up automatically via `.mcp.json`) to persist it.
 
 Steps:
-1. Analyze what the user wants to remember
-2. Extract key concepts (2-5 searchable terms)
-3. Extract relevant file paths if any
-4. Make the API call with the properly escaped content
-5. Confirm to the user that the memory was saved
-6. Show what concepts were tagged for future recall
+1. Analyze what the user wants to remember — pull out the core insight, decision, or fact.
+2. Extract 2-5 searchable `concepts` (lowercased keyword phrases) that capture what the memory is about. Prefer specific terms over generic ones (`"jwt-refresh-rotation"` beats `"auth"`).
+3. Extract any relevant `files` — absolute or repo-relative paths the memory references.
+4. Call `memory_save` with the fields:
+   - `content` — the full text to remember (preserve the user's phrasing as much as possible)
+   - `concepts` — the extracted concept list
+   - `files` — the extracted file list (empty array if none apply)
+5. Confirm to the user that the memory was saved and show the concepts you tagged so they know what terms will retrieve it later.
+
+If `memory_save` isn't available, the stdio MCP shim didn't start — tell the user to:
+1. Run `/plugin list` in Claude Code and confirm `agentmemory` shows as enabled.
+2. Restart Claude Code (the plugin's `.mcp.json` is only read on startup).
+3. Check `/mcp` to see whether the `agentmemory` MCP server is connected.

package/plugin/skills/session-history/SKILL.md

@@ -4,14 +4,15 @@ description: Show what happened in recent past sessions on this project. Use whe
 user-invocable: true
 ---
 
-Fetch recent session history from agentmemory:
+Fetch recent session history using the `memory_sessions` MCP tool (provided by the agentmemory server that this plugin wires up automatically via `.mcp.json`). Pass `limit: 20` to get a meaningful window.
 
-!`curl -s -H "Authorization: Bearer ${AGENTMEMORY_SECRET:-}" "http://${AGENTMEMORY_URL:-localhost:3111}/agentmemory/sessions" 2>/dev/null || echo '{"sessions":[]}'`
+Present the returned sessions in reverse chronological order:
+- Show the session ID (first 8 chars), project, start time, and status
+- For each session with observations, show the key highlights (type + title)
+- Note the total observation count per session
+- If a session summary exists, surface the title and the key decisions
 
-Present the sessions in reverse chronological order:
-- Show session ID (first 8 chars), project, start time, status
-- For each session with observations, show the key highlights
-- Note total observation count per session
-- If summaries exist, show the session title and key decisions
-
-Format as a clean timeline. Do NOT make up sessions -- only show what was returned.
+Format as a clean timeline. **Do NOT make up sessions** — only show what the MCP tool actually returned. If `memory_sessions` isn't available, the stdio MCP shim didn't start — tell the user to:
+1. Run `/plugin list` in Claude Code and confirm `agentmemory` shows as enabled.
+2. Restart Claude Code (the plugin's `.mcp.json` is only read on startup).
+3. Check `/mcp` to see whether the `agentmemory` MCP server is connected.