https://hackerpaper.kaipfister.de/p/2606.10662/Collected HN comments and submissions linking this paper.enSun, 08 Nov 2026 05:37:00 GMThttps://news.ycombinator.com/item?id=50391685urn:hackerpapers:mention:2606.10662:50391685Fri, 06 Nov 2026 12:45:13 GMT<p>Links from the post: [1] Stanford CS146S: How always-on agents work Lecture: https://www.youtube.com/watch?v=L1OBRtfPS34 Slides: https://drive.google.com/file/d/1b8WiBk_lcB3ue-jZMLijSUMLj6S... [2] CMU 11-768 AI Agents: https://www.cmu-agents.com/#/schedule [3] Decentralized Multi-Agent Systems with Shared Context (figure 3, page 3): https://arxiv.org/pdf/2606.10662</p><p><a href="https://hackerpaper.kaipfister.de/p/2606.10662/">Paper and discussion history</a>. A mention is not an endorsement.</p>cs.MAhttps://news.ycombinator.com/item?id=50391647urn:hackerpapers:submission:2606.10662:50391647Fri, 06 Nov 2026 12:40:14 GMT<p>Ask HN: Is anyone running multi/always-on agents that don&#x27;t cost a fortune?</p><p>Yesterday a few interesting links appeared on hacker news about always-on [1] and multi-agent setups [2]. Some of those points resonate with what we&#x27;re experiencing with our current approach of running agents and sub-agents locally. - We are delegating complex and long running tasks to agents more and more. Being able to run those overnight seems like a logical next step in efficiency, because at the moment we are stopping the local agents every evening and restarting them in the morning. - A setup with decentralized multi-agent system with shared context is 5.5x faster than Claude code +…</p><p>6 points; 5 discussion replies on HN. <a href="https://hackerpaper.kaipfister.de/p/2606.10662/">Paper and source history</a>. A submission is not an endorsement.</p>cs.MA