Dual-Memory Complete

A production-oriented dual-store agent memory system: separate tables for memories, core files, and skills in a multi-table vector store, with configurable confidence thresholds and trigger-word driven self-evolution.

View source on GitHub

Key takeaways

• 01

  Separate stores for memories vs skills vs core files

• 02

  Confidence thresholds gate what gets recalled

• 03

  One distinct idea: trigger-word driven memory updates

Flows built on this research

Memory & Context

Cross-Session Project State

Keep long-horizon work coherent across many sessions: externalized project state that any session can load, advance, and hand off.

4 steps · 90-120 minutes