<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reasoning about Intent for Ambiguous Requests · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2511.10453/</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/2511.10453/feed.xml" rel="self" type="application/rss+xml" /><item><title>Reasoning about Intent for Ambiguous Requests — mentioned by jason_oster</title><link>https://news.ycombinator.com/item?id=47042401</link><guid isPermaLink="false">urn:hackerpapers:mention:2511.10453:47042401</guid><pubDate>Tue, 17 Feb 2026 01:02:40 GMT</pubDate><description>&lt;p&gt;I mentioned this in another thread, but this is genuinely demonstrating a known issue with ambiguous prompts. You might be inclined to say, &amp;quot;a human would always interpret the question as having the car nearby the speaker, 50m away from the carwash.&amp;quot; But this is objectively untrue. There are people in this comments section and on the Mastodon thread that found the question to be somewhat confusing. In other words, the premise that &amp;quot;understand[ing] a prompt like a human&amp;quot; is all that&amp;#x27;s needed is wrong because not every human interprets ambiguities in the same way. The human phenomenon is well…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2511.10453/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CL</category></item><item><title>Reasoning about Intent for Ambiguous Requests — mentioned by jason_oster</title><link>https://news.ycombinator.com/item?id=47041866</link><guid isPermaLink="false">urn:hackerpapers:mention:2511.10453:47041866</guid><pubDate>Mon, 16 Feb 2026 23:45:58 GMT</pubDate><description>&lt;p&gt;One of the failure modes I find really frustrating is when I want a coding agent to make a very specific change, and it ends up doing a large refactor to satisfy my request. There is an easy solution, but it requires adding the instructions to the context: Require that any tasks that cannot be completed as requested (e.g., due to missing constraints, ambiguous instructions, or unexpected problems that would lead to unrelated refactors) should not be completed without asking clarifying questions. Yes, the LLM is trained to follow instructions at any cost because that&amp;#x27;s how its reward function…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2511.10453/"&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>
