Engineering
Research
Context windows aren’t memory
Stuffing everything into the prompt feels like memory, but it isn’t. Real systems decide what to retrieve, when, and what to forget — here’s how we think about it.
TAGS
CONTEXT
MEMORY
RAG

Inês Carvalho
ML ENGINEER
2 Jun 2026
6 minutes
ON THIS PAGE
01 Retrieval beats stuffing
02 Forgetting is a feature
03 Memory is a system, not a setting
A bigger context window is not the same as a system that remembers. It’s a bigger desk, not a filing cabinet — everything you put on it is in view at once, and everything you don’t is simply gone.
Retrieval beats stuffing
The instinct is to paste in more: the whole document, the whole history, the whole knowledge base. It works in a demo and falls over in production, where cost, latency, and relevance all degrade as the prompt grows. We retrieve only the few things that matter for this turn and leave the rest out.
Forgetting is a feature
A useful agent decides what to keep. Summaries, not transcripts. State, not logs. The skill isn’t remembering everything — it’s knowing what’s safe to drop so the model spends its attention where it actually counts.
Memory is a system, not a setting
Persistent memory lives outside the model: a store you write to, retrieve from, and can inspect. The context window is just the working surface where the right pieces meet. Treat them as separate and the whole thing gets more reliable — and a lot cheaper to run.
archivio { 1 }
OTHER POSTS
Read related content
Read our posts on strategy, engineering, process, opinion and field notes.
RELATED INSIGHTS
All
Strategy
Engineering
Process
Opinion
Field notes

Most "AI problems" aren’t AI problems
Before you build an agent, it’s worth asking whether the bottleneck is the model — or the broken process around it. Usually it’s the process.
Sofia Almada
5 minutes
Read post

What "production-grade" actually means for an AI agent
A demo proves an agent can work once. Production means it works on the thousandth strange input, at 3am, when nobody’s watching. Here’s the gap between the two.
Inês Carvalho
7 minutes
Read post

The handoff is the product
A system you can’t run without us isn’t an asset — it’s a dependency. We’d rather build something you own outright.
Marco Vieira
4 minutes
Read post

Why we ship in weeks, not quarters
Long timelines hide risk. Short ones surface it. Here’s how a six-week engagement stays honest from kickoff to launch.
Marco Vieira
5 minutes
Read post

Agents vs. wrappers: a field guide
“We added AI” can mean a thin wrapper around a chat box, or a system that does real work end to end. The difference matters more than the label.
Inês Carvalho
6 minutes
Read post
