When Users Change Their Minds: Measuring and Repairing Intent Drift in LLM Agents

Yanjie Zhang, Bowen Cao, Zixin Chen, Yushi Sun

HKUST · CUHK · LIGHTSPEED

Published September 26, 2026 · on the feed October 2, 2026 · ▲ 17 · arXiv 2609.32520

AgentsLanguage & dialogue No code arXiv ↗Hugging Face ↗

The abstract

LLM agents often operate over multi-turn interactions in which user intent changes before execution. We study intent drift: the failure mode in which superseded parts of the user's intent continue to influence the final answer or tool action. We introduce IntentFlux, an executable benchmark that converts verifiable tasks into dialogues with controlled intent changes while preserving their original graders. In a 627-case calibration, mean task score falls from 0.476 to 0.384 as dialogues contain more superseded and withdrawn information. Across eight models, the rate of fully correct solutions is significantly lower when the same final task must be recovered from an evolving dialogue rather than given directly in a single turn. We further introduce StateForge, which explicitly maintains the active requirements before generation. On General-Test, it improves mean task score from 0.367 to 0.467. Providing the ground-truth final state improves performance further but still does not recover single-turn performance, indicating that state-estimation errors explain only part of the gap. These results establish intent drift as a measurable multi-turn failure mode and explicit state maintenance as a partial mitigation.

The Brief

2:16

A short podcast summary of the paper. Written and voiced by AI.

Transcript

When Users Change Their Minds. Measuring and Repairing Intent Drift in LLM Agents. By Yanjie Zhang and three others, from the Hong Kong University of Science and Technology, the Chinese University of Hong Kong, and one other institution. Published on the twenty-sixth of September. No code repository is linked to it.

LLM agents usually work through conversations of several turns, and users change their minds along the way, before anything is executed. The paper names the resulting failure intent drift: parts of what the user wanted earlier, and has since replaced, keep shaping the final answer or the tool action. A task handed over cleanly in one turn does not test for this at all.

IntentFlux is the benchmark built to measure it, and it is executable. It takes tasks that can already be verified and turns them into dialogues with controlled changes of intent, keeping the original graders. The final task is the same one a grader already knows how to check; only the route to it now winds through superseded and withdrawn requests.

Because the graders are preserved, the comparison is clean. The same final task can be posed directly in a single turn, or recovered from an evolving dialogue, and scored the same way. A calibration of six hundred and twenty-seven cases varies how much superseded and withdrawn information the dialogues contain.

In that calibration, mean task score falls from zero point four seven six to zero point three eight four as the dialogues carry more outdated material. Across eight models, the rate of fully correct solutions is significantly lower when the task must be pulled out of an evolving dialogue than when it is given directly.

The authors then try a repair. StateForge explicitly maintains the active requirements before generation. On General-Test it lifts mean task score from zero point three six seven to zero point four six seven. A further experiment hands the model the ground-truth final state. That helps more, but it still does not recover single-turn performance, which suggests that errors in estimating the state account for only part of the gap.

Two results, then, of different strength. Intent drift is established as a failure mode that can be measured, and keeping the current requirements explicit is shown to reduce it. Yet even a perfect record of what the user now wants leaves a shortfall, so part of the problem lies somewhere other than tracking.

Paper Quest · 7 chapters · about 40 min

Play this paper

Learn it by doing: make the calls the authors made, guess the result before you see it, and defend it in a viva graded on your own words. Chapter 1 is right here.

Chapter 1 🧩 · The problem

Every quest starts with a wall. Here it is a user who changed their mind, and an agent that didn't notice.

You build an agent that talks with users over several turns. A user asks for code in one language, later switches language, drops a constraint, then says: go ahead.

The road ahead

  1. 1 · The problem ~6 min When users change their minds mid-conversation, an agent's final answer can still obey requests the user already replaced or withdrew.
  2. 2 · What came before ~3 min
  3. 3 · The key idea ~9 min Before answering, a tracker folds the conversation into an explicit list of active requirements, and the agent solves the task guided by that list.
  4. 4 · Choose your own research ~3 min
  5. 5 · Build the method ~8 min Build dialogues from checkable tasks, grade them like the originals, repair with an explicit active state, then test with the true final state.
  6. 6 · The experiment ~6 min You’ll guess: If an agent is handed the exact ground-truth final requirements of an evolving dialogue, does it match its single-turn performance?
  7. 7 · The viva ~5 min Three questions from the examiners, answered in your own words. Win it for the paper’s trophy.
Join free to play the whole quest ›

Free, with Google or an email address. Your stars and progress are kept.

KipQuest: the day’s AI research, as podcasts and quests. All papers Android app Privacy Contact Episodes are written and voiced by AI from each paper. Summaries can contain mistakes: the paper is the source.