Search
Found 10 articles
A Panorama of Agent Memory Systems: An In-Depth Comparison of Five Approaches in 2026
Memory is the first-principles problem for Agents: an Agent without memory is just an advanced chatbot. This article compares five approaches (agentmemory / PlugMem / Infini-Memory / verifiable-memory / Qdrant+MemoryHub) and provides a scenario selection matrix.
Vector Memory Deep Dive: A Production-Grade Memory System That Ensures AI Agents Never Lose Memory Again
State amnesia is the #1 killer in production Agent environments. We built a four-layer vector memory system based on Qdrant + BGE-m3, with 9 retrieval modes, validated with 6,675 memories in real-world use, raising Chinese search accuracy from 0% to >78%. One line curl | bash, 100% local deployment, and data sovereignty stays in your hands.
The Engineering of AI Memory Retrieval: A Full-Matrix Field Report on Four Access Paths × Ten Scenarios
When an AI assistant needs to "remember everything", how does it retrieve memory? Direct file reads, Qdrant vector search, the MemoryHub capture pipeline, and agentmemory semantic indexing: a field comparison of four paths across ten real scenarios, revealing the boundaries and sweet spots of each path.
A Lightweight Overhaul of MemoryHub in Practice: Cutting from 10 Databases to 5, and RAM from 6.2GB to 500MB
What happens when you delete Neo4j, Elasticsearch, and MongoDB from an AI memory system, keep only the Qdrant + FAISS + SQLite-vec trio, and replace the 9.1GB BGE-m3 with a 193MB bge-small-zh? A complete performance dissection, an embedding model comparison, and a trimming plan aimed at ordinary computers.
Polyglot Persistence in Practice: A Full-Pipeline Evaluation of a Ten-Database Memory System
From BGE-m3 vector embeddings and ten-way synchronized writes to a comparison of search quality and speed across nine backends: a complete stress test of an AI memory system. Qdrant is the king of semantics, FAISS the king of speed, and Neo4j the king of relationships.
MemoryHub v2.0 System Architecture In-Depth Analysis: From Capture Daemon to MCP Real-Time Memory Capture
A complete breakdown of MemoryHub v2.0's dual-mode capture engine, Qdrant vector storage, MCP four-platform integration, Dashboard real-time monitoring, three-layer deduplication, and ten-year lifecycle design.
Complete Comparison of Top 10 Vector and Full-Text Databases: MemoryHub Backend Storage Selection Guide
An in-depth review of ten databases, including Qdrant, Chroma, LanceDB, SQLite-vec, FAISS, Redis, PostgreSQL (pgvector), Elasticsearch, MongoDB Atlas, and Neo4j, in AI memory system scenarios, covering performance, deployment difficulty, resource consumption, and use cases.
MemoryHub Practical Installation and Complete Usage Guide: From Zero to Four Platform Automatic Memory Capture
A step by step guide to installing MemoryHub v2.0: from Docker environment preparation, one click pip installation, four platform MCP configuration, Dashboard usage tips, to the complete process of daily maintenance and troubleshooting.
MemoryHub v2.0 Full Record of Ten-Database Sync: The 6-Hour Battle from 0 Points to 3,892 Records
A complete record of MemoryHub's technical evolution from a monolithic Qdrant to a unified embedding pipeline across ten databases: 18 bug fixes, Python scoping traps, BGE-m3 dimension errors, missing system Python dependencies, and the final architecture that achieves one embedding then ten-database sync.
agentmemory Full Feature Deployment Log: From GitHub Trending to Four Platform Automatic Memory Capture
A complete record of the deep research into agentmemory (13K stars), full feature deployment, OMLX LLM integration, Qdrant dual memory sync, and automatic memory capture configuration for four major platforms: OpenClaw, Claude Code, Hermes, and DeepSeek TUI.