HackerPapers

arXiv:2505.06120cs.CL

LLMs Get Lost In Multi-Turn Conversation

Philippe Laban, Hiroaki Hayashi, Yingbo Zhou, Jennifer Neville

Abstract

Large Language Models (LLMs) are conversational interfaces. As such, LLMs have the potential to assist their users not only when they can fully specify the task at hand, but also to help them define, explore, and refine what they need through multi-turn conversational exchange. Although analysis of LLM conversation logs has confirmed that underspecification occurs frequently in user instructions, LLM evaluation has predominantly focused on the single-turn, fully-specified instruction setting. In this work, we perform large-scale simulation experiments to compare LLM performance in single- and multi-turn settings. Our experiments confirm that all the top open- and closed-weight LLMs we test exhibit significantly lower performance in multi-turn conversations than single-turn, with an average drop of 39% across six generation tasks. Analysis of 200,000+ simulated conversations decomposes the performance degradation into two components: a minor loss in aptitude and a significant increase in unreliability. We find that LLMs often make assumptions in early turns and prematurely attempt to generate final solutions, on which they overly rely. In simpler terms, we discover that *when LLMs take a wrong turn in a conversation, they get lost and do not recover*.

arXiv comments
Journal reference
DOI
Subjects
cs.CLComputation and Language cs.HCHuman-Computer Interaction

On Hacker News

Linked by 3 identifiable commenters in 3 comments across 3 threads, from May 2025 to Dec 2025. Found in 1 HN submission from May 2025 to May 2025. Open submission discussions.

Comments linking this paper, per year.

Discussed in comments3 threads

    • There a recent(ish: May 2025) paper about how drip-feeding information is worse than restarting with a revised prompt once you realize details are missing.[0] [0] https://arxiv.org/abs/2505.06120

      lkbmView on HNParent context

    • Looking at this thread, excited to see the community articulating what many of us have been experiencing. The shift from "prompt engineering" to "context engineering" really captures what's happening. The technical stuff (RAG, vector databases) is getting commoditized. But…

      mrcodersView on HNParent context

    • That's why in practice you need more than this simple loop! Pretty much WIP, but I am experimenting with simple sequence-based workflows that are designed to frequently reset the conversation [2] This goes well with Microsoft paper "LLMs Get Lost In Multi-Turn Conversation "…

      hbbioView on HNParent context

Submitted to Hacker News

Connected through shared HN threads, not inferred similarity or a recommendation.