Persisting agent state across sessions using database backends, file storage, vector store persistence, and conversation serialization. Comparison of approaches with implementation patterns.

Every time you start a new session with an LLM agent, it wakes up blank. It does not remember preferences, project context, decisions from last week, or anything from prior sessions. This “goldfish memory” problem is the single biggest practical limitation of LLM agents for real-world use.¹⁾²⁾

Memory persistence solves this by storing agent state durably and retrieving it at session start. Persistent storage systems for agent context, history, and learning across sessions are necessary for continual learning and adaptive agent behavior in open-world tasks.³⁾ The right approach depends on your scale, query patterns, and whether you need semantic retrieval or structured lookups. In multi-tenant or collaborative environments, synchronization mechanisms for shared state become critical, enabling agents to access and update context collectively.⁴⁾

A specialized approach to memory persistence involves background agents that capture screen context and environment state to build continuous memory of user activities and system state, maintaining awareness across sessions without explicit user intervention.⁵⁾-catch-up|The Rundown AI - Persistent Memory Agents (2026]]))

Enterprise platforms like the Gemini Enterprise Agent Platform offer integrated persistent memory banks—storage and retrieval systems that enable agents to maintain context and learning across sessions and interactions, supporting stateful agent operations at scale.⁶⁾

Best for production systems needing both structured queries and semantic search.

• ACID transactions for reliable state persistence
• pgvector extension enables vector similarity search alongside relational queries
• Auditable with full query logging
• Scales well with connection pooling and read replicas

Best for high-speed session state and short-term memory caching.⁷⁾

• In-memory speed: 1-10ms reads/writes
• Supports vectors via RediSearch module
• Pub/sub for real-time multi-agent coordination
• Configure AOF persistence for durability

Best for single-agent systems, prototypes, and embedded deployments.

• Serverless, zero configuration
• Full SQL support in a single file
• Limited concurrency (file locking)
• Scales to ~10K records comfortably

import json
from datetime import datetime, timezone
from typing import Optional
 
import asyncpg
 
 
class AgentMemoryStore:
    """Persistent agent memory using [[postgresql|PostgreSQL]] with [[pgvector|pgvector]]."""
 
    def __init__(self, dsn: str):
        self.dsn = dsn
        self.pool = None
 
    async def initialize(self):
        self.pool = await asyncpg.create_pool(self.dsn)
        async with self.pool.acquire() as conn:
            await conn.execute("""
                CREATE EXTENSION IF NOT EXISTS vector;
                CREATE TABLE IF NOT EXISTS agent_memories (
                    id SERIAL PRIMARY KEY,
                    agent_id TEXT NOT NULL,
                    memory_type TEXT NOT NULL,
                    content TEXT NOT NULL,
                    embedding vector(1536),
                    metadata JSONB DEFAULT '{}',
                    created_at TIMESTAMPTZ DEFAULT NOW(),
                    accessed_at TIMESTAMPTZ DEFAULT NOW(),
                    relevance_score FLOAT DEFAULT 1.0
                );
                CREATE INDEX IF NOT EXISTS idx_memories_agent
                    ON agent_memories(agent_id, memory_type);
                CREATE INDEX IF NOT EXISTS idx_memories_embedding
                    ON agent_memories USING ivfflat (embedding vector_cosine_ops);
            """)
 
    async def store(
        self,
        agent_id: str,
        content: str,
        memory_type: str = "long_term",
        embedding: Optional[list[float]] = None,
        metadata: Optionaldict = None,
    ):
        async with self.pool.acquire() as conn:
            await conn.execute(
                """INSERT INTO agent_memories
                   (agent_id, memory_type, content, embedding, metadata)
                   VALUES ($1, $2, $3, $4, $5)""",
                agent_id, memory_type, content, embedding,
                json.dumps(metadata or {}),
            )
 
    async def recall_semantic(
        self,
        agent_id: str,
        query_embedding: listfloat,
        limit: int = 10,
        score_threshold: float = 0.7,
    ) -> listdict:
        async with self.pool.acquire() as conn:
            rows = await conn.fetch(
                """SELECT content, metadata,
                       1 - (embedding <=> $2) AS similarity
                   FROM agent_memories
                   WHERE agent_id = $1
                     AND 1 - (embedding <=> $2) > $3
                   ORDER BY similarity DESC
                   LIMIT $4""",
                agent_id, query_embedding, score_threshold, limit,
            )
            return [dict(r) for r in rows]
 
    async def recall_recent(
        self, agent_id: str, memory_type: str, limit: int = 20
    ) -> listdict:
        async with self.pool.acquire() as conn:
            rows = await conn.fetch(
                """SELECT content, metadata, created_at
                   FROM agent_memories
                   WHERE agent_id = $1 AND memory_type = $2
                   ORDER BY created_at DESC LIMIT $3""",
                agent_id, memory_type, limit,
            )
            return [dict(r) for r in rows]

The simplest approach: store memory as human-readable markdown files. Used by soul.py and Claude's MEMORY.md pattern.⁸⁾⁹⁾

• Zero dependencies, human-readable, easy to debug
• Files organized by date or topic
• Agent reads memory files at session start, writes updates as it works
• Limited concurrency and no semantic search without additional tooling

Structure: SOUL.md (identity/persona) + MEMORY.md (curated long-term facts) + memory/YYYY-MM-DD.md (daily session logs).

Persist embeddings for semantic retrieval using Qdrant, Chroma, pgvector, or similar.

• Store facts extracted from conversations as embeddings
• Retrieve relevant memories via similarity search at query time
• Combine with structured storage for hybrid retrieval
• Frameworks like Mem0 automate fact extraction from conversations and store in vector backends¹⁰⁾

Dump full chat histories or agent states to JSON/YAML for reload.

• Simple and portable, works with any storage backend
• Bloats context without indexing or summarization
• LangGraph uses checkpoint-based serialization: graph.get_state(checkpoint_id)
• Best used with summarization to compress old conversations before storage

• Temporal decay, Reduce relevance scores over time; forget stale memories
• Consolidation, Periodically summarize episodic memories into long-term facts
• Deduplication, Merge similar memories to prevent bloat
• Capacity limits, Set maximum memory counts per agent and evict by relevance
• Privacy, Implement deletion APIs for user data removal (GDPR compliance)

• Mem0, Automated memory extraction, vector + graph storage, multi-provider support
• LangGraph, Checkpoint-based persistence with pluggable backends (SQLite, PostgreSQL, Redis)
• soul.py, File-based memory with markdown files, zero dependencies
• CrewAI / AutoGen, Message list serialization with configurable storage

• Session Persistence
• Agent Memory Frameworks
• File System-Based Memory for Agents
• Long-Term Memory
• Traditional Agent State vs Managed Agents Session State