← Agent MemoryCONTENT HISTORY

Update to Agent Memory

Snapshot Oct 29, 2026 · 12:08 UTC · version 0.9.30

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Agent Memory and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Search agentmemory for past observations, sessions, and learnings about a topic using hybrid BM25 plus vector plus graph search. Use when the user says \"recall\", \"what did we do about\", \"did we ever\", \"have we seen\", or needs context from past sessions.",
  "included_files": [
    {
      "relative_path": "EXAMPLES.md",
      "size_in_bytes": 1606
    }
  ],
  "name": "recall",
  "skill_md_contents": "---\nname: recall\ndescription: Search agentmemory for past observations, sessions, and learnings about a topic using hybrid BM25 plus vector plus graph search. Use when the user says \"recall\", \"what did we do about\", \"did we ever\", \"have we seen\", or needs context from past sessions.\nargument-hint: \"[search query]\"\nuser-invocable: true\n---\n\nThe user wants to recall past context about: $ARGUMENTS\n\n## Quick start\n\n```json\nmemory_smart_search { \"query\": \"jwt refresh token rotation\", \"limit\": 10 }\n```\n\nExpected output:\n\n```text\n2 results across 2 sessions.\n[importance 8] decision · \"Rotate refresh tokens on every use\" (session 7f3a9c21)\n[importance 5] code · \"limit.ts counts per-IP\" (session b21d004e)\n```\n\n## Why\n\nOnly surface what the tool returned. Never fabricate an observation, a session\nid, or an importance score. If nothing comes back, say so.\n\n## Workflow\n\n1. Call `memory_smart_search` with the user's text as `query` and `limit: 10`.\n   Pass `project` when the user scopes to a specific repo.\n2. Group results by session. Records carry a provenance channel (`user`, `agent`,\n   `tool`, `import`, `shared`); when results conflict, prefer `user` over `agent`\n   inference, and flag `shared` records as another teammate's write.\n3. For each observation show its type, title, and narrative.\n4. Lead with the high-signal observations (importance >= 7).\n5. If zero results, suggest 2-3 alternative search terms and stop. Do not guess.\n\n## Anti-patterns\n\nWRONG: results are empty, so you write \"We probably discussed token expiry last\nweek\" from assumption.\n\nRIGHT: \"No memories matched that query. Try `refresh token`, `session expiry`,\nor `auth rotation`.\"\n\n## Checklist\n\n- Every observation shown came from the tool response.\n- Results grouped by session, high-importance first.\n- Empty results trigger alternative-term suggestions, not invention.\n- No session id or score was paraphrased or rounded.\n\n## See also\n\n- `remember`: the write side; recall retrieves what it stores.\n- `recap`, `handoff`, `session-history`: session-scoped views of the same data.\n- `memory-discipline`: when to run this search unprompted.\n\n## Troubleshooting\n\nSee ../_shared/TROUBLESHOOTING.md if `memory_smart_search` is not available.\n"
}

SHA-256 of public snapshot: 1e41564c9e218eb8864e60ef984b56f29f67f2d9ea0184df9c7c50e56fb06464