Yourmemory

What is Yourmemory?

Yourmemory provides persistent, self-improving memory for AI agents, built on the science of how humans remember. It integrates with any MCP client (Claude, Cursor, Cline, Windsurf) and runs entirely on your machine with no API key required.

How to use Yourmemory?

Install with pip install yourmemory, then run yourmemory-register <your-token> and yourmemory-setup. Optionally download a standalone binary from the latest release. Start the server with no arguments. Works out of the box with DuckDB (default) or Postgres with pgvector for teams.

Key features of Yourmemory

• Consolidation: compresses related facts into clean summaries.
• Biological decay: memories fade on the Ebbinghaus forgetting curve.
• Entity graph: memories link by shared people, places, and concepts.
• Survives context resets: hands back working context after compaction.
• Tamper-evident audit trail: hash-chained ledger logs every operation.
• Team memory pools: role-based shared and private memory.
• Data rights: export and right‑to‑forget with one command.
• MCP‑native and local‑first: no external API or cloud dependency.

Use cases of Yourmemory

• AI agents remembering user preferences and context across sessions.
• Teams sharing institutional knowledge with role‑based access.
• Long‑running tasks that need to survive context window resets.
• Compliance‑heavy environments requiring an auditable memory trail.
• Research and experimentation with memory consolidation and decay.

FAQ from Yourmemory

What makes Yourmemory different from other memory tools?

It uses consolidation, biological decay, an entity graph, and hybrid retrieval — not just a vector database. Memory gets sharper over time and recalls what you forgot to ask for.

What are the runtime requirements?

Python 3.11–3.14. No Docker or database setup is needed. All memory is stored locally in ~/.yourmemory/ by default (DuckDB). Optionally install Ollama for better local fact extraction.

Where does my data live?

All data is stored locally on your machine. DuckDB is the default backend; you can switch to Postgres with the pgvector extension for shared or production use.

How does memory decay work?

Each memory ages on an Ebbinghaus forgetting curve. Stale, unused facts fade, while frequently recalled ones persist. Different categories (strategy, fact, assumption, failure) have different half‑lives.

Is there an audit trail?

Yes. Every read, write, update, delete, and consolidation is appended to a hash‑chained, tamper‑evident audit log. Altering one record breaks the chain.