Show HN: AI memory with biological decay (52% recall)
YourMemory introduces a persistent, biologically inspired memory system for AI agents that mimics human memory with decay and recall dynamics. It uses the Ebbinghaus forgetting curve to let important memories persist while fading less relevant ones, and combines vector search with graph-based context expansion. The system shows 59% recall on a multi-session benchmark, nearly double that of Zep Cloud. It integrates easily with MCP-compatible AI clients and requires no infrastructure setup.
- ▪YourMemory achieves 59% Recall@5 on the LoCoMo-10 benchmark, outperforming Zep Cloud's 28%.
- ▪Memory strength decays over time based on the Ebbinghaus forgetting curve, modulated by importance and recall frequency.
- ▪The system uses hybrid retrieval combining vector similarity and graph-based context expansion to surface related memories.
- ▪Memories are categorized by persistence level, with strategy memories lasting up to 38 days without recall.
- ▪YourMemory supports multi-agent setups with private and shared memory spaces via API key authentication.
Full article excerpt tap to expand
YourMemory Persistent memory for AI agents — built on the science of how humans remember. The Problem Every session, your AI assistant starts from zero. It asks the same questions, forgets your preferences, re-learns your stack. There is no memory between conversations. YourMemory fixes that. It gives AI agents a persistent memory layer that works the way human memory does — important things stick, forgotten things fade, outdated facts get replaced automatically. Two commands to install, zero infrastructure required. How Well Does It Work? Tested on LoCoMo-10 — 1,534 QA pairs across 10 multi-session conversations. System Recall@5 95% CI YourMemory (BM25 + vector + graph + decay) 59% 56–61% Zep Cloud 28% 26–30% 2× better recall than Zep Cloud on the same benchmark. Full methodology and per-sample breakdown in BENCHMARKS.md. Writeup: I built memory decay for AI agents using the Ebbinghaus forgetting curve. Demo Quick Start Supports Python 3.11, 3.12, 3.13, and 3.14. No Docker, no database setup, no external services. Step 1 — Install pip install yourmemory Step 2 — Run setup (once) yourmemory-setup Downloads the spaCy language model and initialises the local database at ~/.yourmemory/memories.duckdb. Step 3 — Get your config path yourmemory-path Prints your full executable path and a ready-to-paste config block. Copy it. Step 4 — Wire into your AI client Claude Code Add to ~/.claude/settings.json: { "mcpServers": { "yourmemory": { "command": "yourmemory" } } } Reload (Cmd+Shift+P → Developer: Reload Window). Claude Desktop Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows): { "mcpServers": { "yourmemory": { "command": "yourmemory" } } } Restart Claude Desktop. Cline (VS Code) VS Code doesn't inherit your shell PATH. Run yourmemory-path first to get the full executable path. In Cline → MCP Servers → Edit MCP Settings: { "mcpServers": { "yourmemory": { "command": "/full/path/to/yourmemory", "args": [], "env": { "YOURMEMORY_USER": "your_name" } } } } Restart Cline after saving. Cursor Add to ~/.cursor/mcp.json: { "mcpServers": { "yourmemory": { "command": "/full/path/to/yourmemory", "args": [], "env": { "YOURMEMORY_USER": "your_name" } } } } OpenCode Add to ~/.config/opencode/config.json: { "mcp": { "yourmemory": { "type": "local", "command": ["yourmemory"], "environment": { "YOURMEMORY_USER": "your_name" } } } } Then copy the memory workflow instructions: cp sample_CLAUDE.md ~/.config/opencode/instructions.md Restart OpenCode. Any MCP-compatible client: YourMemory is a standard stdio MCP server. Works with Windsurf, Continue, Zed, and any client that supports MCP. Use the full path from yourmemory-path if the client doesn't inherit shell PATH. Step 5 — Add memory instructions to your project cp sample_CLAUDE.md CLAUDE.md Edit CLAUDE.md — replace YOUR_NAME and YOUR_USER_ID. Claude now follows the recall → store → update workflow automatically on every task. MCP Tools Three tools. Called by Claude automatically once CLAUDE.md is in place. Tool When What it does recall_memory(query) Start of every task Surfaces relevant memories ranked by similarity × strength store_memory(content, importance) After learning something new Embeds and stores with biological decay update_memory(id, new_content) When a memory is outdated Re-embeds and replaces # Example session store_memory("Sachit prefers tabs over spaces in Python", importance=0.9, category="fact") # Next…
This excerpt is published under fair use for community discussion. Read the full article at GitHub.