0Pricing
Claude Architect · Lesson

Case-Facts Blocks & Trimming Output

Pin facts outside the summary; trim verbose tool results.

The Long-Conversation Problem

In a long agentic conversation, the full message history grows past what's comfortable to keep in context. The common fix is progressive summarization: compress older turns into a running summary so the window stays manageable.

But summarization has a quiet failure mode. It's great at preserving the gist of a conversation and terrible at preserving exact values. As you compress, the precise things a model needs to act correctly start to blur.

What Summarization Destroys

Progressive summarization makes numbers, percentages, and dates vague. A turn that said "order #88231 shipped 2026-03-14, refund of $412.50 approved" can degrade into "the customer's order shipped recently and a refund was approved."

That's fine for narrative flow, but catastrophic for a tool-calling agent that must pass order_id=88231 or reason about a $412.50 threshold. The model can't recover a value the summary already erased.

All lessons in this course

  1. Full History Is Required
  2. Progressive Summarization Risks
  3. Lost-in-the-Middle Effect
  4. Case-Facts Blocks & Trimming Output
← Back to Claude Architect