<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Needle in the Haystack for Memory Based Large Language Models · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2407.01437/</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/2407.01437/feed.xml" rel="self" type="application/rss+xml" /><item><title>Needle in the Haystack for Memory Based Large Language Models — mentioned by yompal</title><link>https://news.ycombinator.com/item?id=43246509</link><guid isPermaLink="false">urn:hackerpapers:mention:2407.01437:43246509</guid><pubDate>Mon, 03 Mar 2025 20:48:46 GMT</pubDate><description>&lt;p&gt;LLMs do well with outcome-described tools and APIs are written as resource-based atomic actions. By describing an API as a collection of outcomes, LLMs don&amp;#x27;t need to re-reason each time an action needs to be taken. Also, when an OpenAPI spec gets sufficiently big, you face a need-in-the-haystack problem https://arxiv.org/abs/2407.01437.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2407.01437/"&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>
