Highcoordination

Context Drift

Important context information is lost or distorted as it passes through multiple agent handoffs.

Overview

How to Detect

Later agents miss critical details from early conversation. Decisions are made without full context. Users need to repeat information. Outputs contradict earlier inputs.

Root Causes

Token limits force context compression. Agents summarize without preserving critical details. No structured context schema. Long conversation chains without checkpoints.

Test your agents against this failure mode
Try Playground

Deep Dive

Overview

When context passes through multiple agents, important details can be lost or distorted. Each handoff increases the risk of losing key information, especially in long, multi-step conversations.

Drift Mechanisms

Summarization Loss

Each agent may summarize context before passing it on:

Original: "Client prefers blue, but will accept navy or sky blue,
         NOT royal blue which they had issues with last time."

After 3 handoffs: "Client prefers blue."

Priority Inversion

Less important information displaces critical context due to token limits.

Semantic Shift

Meaning changes subtly through paraphrasing:

Original: "Handle with care" (fragile item)
Drift: "Handle with care" (sensitive topic)

Temporal Confusion

Agents lose track of what happened when:

"They said they'd call back" - Was this yesterday? An hour ago? In the original request?

Impact Scenarios

Customer Service

Customer explains complex issue to Agent A. By the time it reaches Agent D, the core problem is obscured by later conversation.

Research Pipeline

Key constraints from the original request are lost, leading to research that doesn't address the actual question.

Multi-Step Reasoning

Intermediate conclusions drop critical caveats, leading to overconfident final answers.

Detection Approaches

Context Checksum

Include critical facts in a structured summary that's validated at each step:

{
  "core_requirements": ["blue preferred", "not royal blue"],
  "constraints": ["budget under $1000"],
  "checksum": "abc123"
}

Semantic Similarity Tracking

Compare context embeddings before and after each handoff:

if cosine_sim(original_context, current_context) < 0.85:
    alert("Significant context drift detected")

Key Entity Tracking

Ensure all mentioned entities remain in downstream context.

How to Prevent

Structured Context Schemas: Define explicit fields for critical context that must be preserved.

Context Checkpoints: Periodically verify that original requirements are still present.

Reference Back: Store full context externally; pass references instead of summaries.

Critical Fact Marking: Tag information that must never be dropped.

Drift Detection: Compare context similarity across handoffs and alert on significant changes.

Want expert guidance on implementation?
Get Consulting

Real-World Examples

In a complex legal research task, a multi-agent system lost track of a critical jurisdiction constraint after the fourth handoff, resulting in research under the wrong legal framework.