Agentic Research

Search

Found 5 articles

Evidence

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.

2026/06/10 · Vector Memory · Qdrant · Retrieval
Evidence

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.

2026/05/23 · AI Memory · Qdrant · MemoryHub
Evidence

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.

2026/05/23 · MemoryHub · BGE-m3 · Vector Database
Evidence

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.

2026/05/22 · MemoryHub · Vector Database · Benchmark
Playbooks

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.

2026/05/21 · MemoryHub · Development Retrospective · Pitfalls