<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Intent Mismatch Causes LLMs to Get Lost in Multi-Turn Conversation · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2602.07338/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2602.07338/feed.xml" rel="self" type="application/rss+xml" /><item><title>Intent Mismatch Causes LLMs to Get Lost in Multi-Turn Conversation — mentioned by jameslk</title><link>https://news.ycombinator.com/item?id=47788146</link><guid isPermaLink="false">urn:hackerpapers:mention:2602.07338:47788146</guid><pubDate>Thu, 16 Apr 2026 03:01:47 GMT</pubDate><description>&lt;p&gt;&amp;gt; I queued the work and let it run. First task came back good. Second came back good. Somewhere around hour four the quality started sliding. By hour six the agent was cutting corners I’d specifically told it not to cut, skipping steps I’d explicitly listed, behaving like I’d never written any of the rules down. &amp;gt; … &amp;gt; When I write a prompt, the agent doesn’t just read the words. It reads the shape. A short casual question gets read as casual. A long precise document with numbered rules gets read as… not just the rules, but also as a signal. “The user felt the need to write this much.” “Why?”…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2602.07338/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item></channel></rss>
