Back to directory

AutoMem

A long-term memory service for AI assistants that combines a graph database of typed relationships with a vector index, so an assistant can recall the reasoning behind a decision rather than only similar past text.

AutoMem

AutoMem gives an AI assistant a memory that persists across sessions. It stores the decisions, preferences, notes and context a user wants recalled, so tools such as Claude, Cursor, Codex or ChatGPT can retrieve the right detail later instead of the conversation starting over each time.

It combines two storage layers: FalkorDB holds memories as graph nodes with eleven typed relationships between them, so a decision, its rationale and its consequences can be followed as connected facts rather than only matched by similarity; Qdrant provides the vector index used for semantic lookup. Retrieval runs directly against these stores without an extra generation call in the middle, using embeddings from Voyage, OpenAI or a local provider.

It runs locally with Docker, on a user's own infrastructure, or as a small hosted service group, and exposes both an MCP bridge for desktop and CLI clients and a REST API for cloud agents.

More in Agent memory

See all 450
  • A long technical guide to AI agent memory: why stateless LLMs need it, the different memory architectures from vector stores to knowledge graphs, and how Cognee implements one as an open-source memory layer.

  • A local, file-based long-term memory layer for a personal AI that never summarizes conversations, keeping every line with a timestamp and searching by time first and words second, rather than retrieving only similar-seeming chunks.

  • NEOTH

    deepwiki.com

    A local-first personal AI daemon in Rust with five memory tiers, consent-gated tools, a WASM plugin sandbox, multi-provider model routing and signed audit logs, aimed at people who want both a daily assistant and a serious coding helper.