Terms  /  Execution Quality  /  Plan Drift
04 · Execution Quality

Plan Drift

Deviation from the original plan over time.

Plan Drift is gradual and often well-intentioned. The agent encounters an unexpected issue and adjusts its approach. It finds a "better" way to implement something and silently changes course. It gets sidetracked by a related problem and follows that thread instead. Each individual deviation might make sense in isolation, but cumulatively they mean the agent is no longer working on the plan it was given. Plan Drift is particularly dangerous because the agent often believes it's still following the plan — it's just "adapting." Without inspection, the user won't realize the drift until the final output doesn't match expectations.

Example
An agent is tasked with building a REST API for user management. By turn 20, it has decided to add a GraphQL layer "for flexibility," restructured the database schema to support multi-tenancy (not requested), and is now building an admin dashboard. Each decision felt logical in the moment, but the agent has drifted far from the original plan. The user asked for a simple REST API and got a half-finished platform. The agent describes this as "taking a more comprehensive approach." It's Plan Drift.

More in Execution Quality