Agent Memory Is Three Postgres Extensions in a Trench Coat

Thursday, October 01 · 11:30–12:20
Cover (Sponsor) Beginner

Ask a vendor what agent memory is and you get an architecture diagram with four databases on it. It can be one. Every fact an agent stores lands three ways in parallel: raw text for full-text search, an embedding in pgvector, and entity-relationship triples extracted into an Apache AGE graph. Retrieval is one hybrid query across all three, because each index catches recall the other two miss.

In this session, we discuss how Meko gives your agents a shared data layer. We will cover datapack blueprints: six decisions about what to remember, share, never stop and prove, compared across three use cases.