Lost in the Middle: how language models use long contexts
Listed inLong Context ProcessingContext Engineeringon
The paper behind the U-shaped recall curve: models attend to the start and end of a long context and lose the middle.
Deciding what goes into the window, what gets compacted, and what never should have been there.
Sign in to track your progress across sections.
17 articles
Listed inLong Context ProcessingContext Engineeringon
The paper behind the U-shaped recall curve: models attend to the start and end of a long context and lose the middle.
Listed inWhat is a Context Layer?Context Engineeringon
One place in the codebase that decides what goes into every prompt. The limit that binds is the model's attention rather than the size of the context window, so the layer curates what it sends instead of filling the space available.
Listed inContext EvaluationContext Engineeringon
Wrong answer or missing context? Precision has a reference-free variant you can run today; recall always needs ground truth.
Listed inContext EngineeringContext Engineeringon
Five things make up the payload, and each is a decision with its own failure. Tool definitions are billed on every call whether used or not.
Listed inLong Context ProcessingContext Engineeringon
The curve is U-shaped and the middle is the weak spot, even for models trained for long context. Where to put what matters.
Listed inAtlanContext Engineeringon
The context an assistant needs for warehouse data is metadata, not rows. Certification is what makes it trustworthy enough to act on.
Listed inContext IsolationContext Engineeringon
Running a sub-task in its own context window keeps its exploration out of the main conversation, which can return a short result from a long search. The same separation is a normative rule in the Model Context Protocol, and it costs the caller information the sub-task never reports.
Listed inState & Historical ContextContext Engineeringon
Twenty turns into a booking, six settled facts are what the model needs and the transcript is an inefficient way to carry them. Trimming a turn per request can also cost more than sending everything, because it breaks the cache.
Listed inContext SourcesContext Engineeringon
Docs, databases, tickets, telemetry, and the user's own session.
Listed inMemory SystemsContext Engineeringon
Short-term, episodic, and semantic memory across sessions.
Listed inPrompt vs Context EngineeringContext Engineeringon
Wording the ask vs assembling everything the model needs to answer it.
Listed inContext SecurityContext Engineeringon
Treating retrieved content as untrusted input, because it is.
Listed inDataHubContext Engineeringon
Open-source metadata platform for lineage-aware context sources.
Listed inContext Failure ModesContext Engineeringon
Poisoning, distraction, confusion, and clash — the four ways context degrades.
Listed inMulti-Agent Context SharingContext Engineeringon
Passing just enough between agents to avoid both amnesia and blowup.
Listed inContext CompactionContext Engineeringon
Summarising and pruning history so long sessions stay affordable.
Listed inExternal MemoryContext Engineeringon
Offloading state to files, databases, and scratchpads outside the window.