#memory
Every post tagged "memory".
27 posts · showing 21–27
-
Chunking for Agents Is Not Chunking for Search
Search results are read by a person who fills in the gaps. An agent doesn't — it acts on the fragment. That one difference changes how you chunk, how many you return, and what "no results" should mean.
-
Run, Session, or Global? Scoping Agent Memory Correctly
Too-small a scope produces a visible annoyance; too-large produces a silent wrong answer. One question assigns any fact correctly, and one rule keeps multi-tenant reads from becoming an incident.
-
Vector Database or Postgres? Choosing Storage for Agent Memory
Most agent memory reads are filtered similarity or plain structured lookup — relational workloads wearing an embedding. Write down your ten most common retrievals before you add a second database.
-
Where You Put Things in the Context Changes the Answer
Same instructions, same documents, different results — because the constraint sat in the middle of a long array. Two ordering rules, one of which also decides whether your prompt cache ever hits.
-
What Belongs in Long-Term Memory (and What's Just Transcript)
Embedding every turn gives you a transcript with a search box, not memory. Three categories deserve to outlive a conversation — and the contradiction problem needs deciding before it arrives, not after.
-
Trim, Summarize, or Retrieve? Three Ways to Survive a Long Agent Run
Trimming loses the oldest information, summarizing loses specificity, retrieval loses whatever the query missed. Which loss your run can survive is the whole decision — plus one rule that prevents most long-run failures.
-
Why Your Agent Forgets Step 2 by Step 7 — And Four Ways to Keep the Thread
Agents rarely fail because they reason badly — they fail because the original instruction gets buried under accumulated tool output. Here's how to tell displacement from dilution, and four fixes that keep the thread intact.