What is the taxonomy of Agent Drift in LLM orchestration?

As enterprise engineering teams deploy autonomous AI Agents (systems capable of executing multi-step workflows across external tools), a new systemic failure state has emerged: Agent Drift. Agent Drift occurs when an LLM slowly deviates from its initial directive during an extended multi-step orchestration loop, resulting in mathematically unpredictable, often catastrophic, end-states.

The Taxonomy of Drift

Founders must understand the taxonomy of these failures before authorizing autonomous systems access to production APIs or databases. There are three primary classifications of Agent Drift in modern LLM architectures:

The Executive Case Study

A fast-growing FinTech startup deployed a LangChain-based "Autonomous Due Diligence Agent" to scrape competitor pricing tiers and update an internal HubSpot CRM database. During a routine weekend run, a competitor updated their website with an aggressive Cloudflare captcha. Encountering the unexpected HTML, the Agent suffered Cyclic Loop Drift. It requested the URL 45,000 times, attempting to parse the captcha as JSON. Because the engineer failed to put a "Max Iteration Hook" in the ReAct loop, the Agent burned $16,000 in OpenAI tokens fighting a Captcha for 48 hours before the CEO forced a manual kill-switch.

The 90-Day Remediation Plan

• Day 1-30: Enforce strict Max-Step Constraints. If you are using ReAct or Plan-and-Execute loops, hardcode an execution cap (e.g., maximum 10 loops). If the agent cannot solve it in 10 steps, gracefully degrade to a human-in-the-loop escalation.
• Day 31-60: Implement "Context Anchoring." Programmatically inject the Prime Directive (the original goal) into the system prompt recursively at every 5th iteration loop to prevent Context Eviction.
• Day 61-90: Build a simulated evaluation environment. Before deploying an agent to production CRM or DB tools, force it to run through a gauntlet of 50 edge-case "Drift Scenarios" (broken APIs, unexpected 404s, massive JSON payloads) to monitor its resiliency.