<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: 8dazo</title><link>https://news.ycombinator.com/user?id=8dazo</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 08 Apr 2026 17:04:54 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=8dazo" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by 8dazo in "GLM-5.1: Towards Long-Horizon Tasks"]]></title><description><![CDATA[
<p>Just saw the Claude Mythos post. Not sure when it’s going public, but this feels like a real jump, not just incremental progress. Also waiting for the next GLM release coz specs are looking kind of insane.</p>
]]></description><pubDate>Wed, 08 Apr 2026 00:30:58 +0000</pubDate><link>https://news.ycombinator.com/item?id=47683159</link><dc:creator>8dazo</dc:creator><comments>https://news.ycombinator.com/item?id=47683159</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47683159</guid></item><item><title><![CDATA[Ask HN: Is there any tool that can stop LLM calls at runtime (not just monitor)?]]></title><description><![CDATA[
<p>I’ve been running into cases where LLM/agent systems make unexpected or repeated calls and costs spike quickly.<p>Most tools I’ve found focus on observability (logs, traces, dashboards), but not actual enforcement.<p>Is there anything that can:<p>- stop or cut off a call mid-execution (based on budget, tokens, or conditions)?<p>- enforce limits at runtime instead of just alerting after the fact?<p>Curious if people here are solving this in practice, or just handling it at the application level.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47683113">https://news.ycombinator.com/item?id=47683113</a></p>
<p>Points: 3</p>
<p># Comments: 0</p>
]]></description><pubDate>Wed, 08 Apr 2026 00:26:56 +0000</pubDate><link>https://news.ycombinator.com/item?id=47683113</link><dc:creator>8dazo</dc:creator><comments>https://news.ycombinator.com/item?id=47683113</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47683113</guid></item><item><title><![CDATA[Ask HN: How are you controlling costs and enforcing limits for LLM calls?]]></title><description><![CDATA[
<p>I’ve been running into an issue with LLM/agent systems where unexpected loops or repeated calls can quickly drive up costs.<p>Most tools I’ve seen focus on observability (logs, traces, dashboards), but not actual enforcement at runtime.<p>Curious how people here are handling this in production:<p>- Are you enforcing hard limits (budget, rate, etc.) or just monitoring?<p>- Do you handle this at the app level or via some middleware/proxy?<p>- Have you built something in-house for this?<p>Feels like an unsolved problem, especially with agents.<p>Would love to hear how others are dealing with it.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47671453">https://news.ycombinator.com/item?id=47671453</a></p>
<p>Points: 3</p>
<p># Comments: 2</p>
]]></description><pubDate>Tue, 07 Apr 2026 06:33:36 +0000</pubDate><link>https://news.ycombinator.com/item?id=47671453</link><dc:creator>8dazo</dc:creator><comments>https://news.ycombinator.com/item?id=47671453</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47671453</guid></item><item><title><![CDATA[New comment by 8dazo in "Ask HN: Who wants to be hired? (April 2026)"]]></title><description><![CDATA[
<p>Location: India
Remote: Yes
Willing to relocate: Yes (preferably Europe / CET-aligned roles)
Technologies: TypeScript, JavaScript, Node.js, Next.js, React, PostgreSQL, MongoDB, REST APIs, GraphQL, Docker, AWS, Tailwind, Supabase (basic), AI/LLM integrations
Résumé/CV: <a href="https://drive.google.com/file/d/1Dfk5KNSDaDLQ_6EbVvzwdPJOmrJOfFHc/view?usp=sharing" rel="nofollow">https://drive.google.com/file/d/1Dfk5KNSDaDLQ_6EbVvzwdPJOmrJ...</a>
Email: devansh21y@gmail.com</p>
]]></description><pubDate>Tue, 07 Apr 2026 06:26:17 +0000</pubDate><link>https://news.ycombinator.com/item?id=47671396</link><dc:creator>8dazo</dc:creator><comments>https://news.ycombinator.com/item?id=47671396</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47671396</guid></item><item><title><![CDATA[New comment by 8dazo in "Show HN: PhoneClaw – Replace a $20/mo VPS with an old Android phone"]]></title><description><![CDATA[
<p>That's actually the goal! PhoneClaw isn't replacing the AI model; it's replacing the VPS.<p>Your AI can generate the code or the text (like the gym plan), but it needs a place to run 24/7 to actually execute tasks, save files, or interact with APIs. Usually, you'd pay for a cloud server to host that logic. PhoneClaw lets you host that execution layer on a spare phone you already own.</p>
]]></description><pubDate>Tue, 17 Feb 2026 03:27:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=47043378</link><dc:creator>8dazo</dc:creator><comments>https://news.ycombinator.com/item?id=47043378</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47043378</guid></item><item><title><![CDATA[Show HN: PhoneClaw – Replace a $20/mo VPS with an old Android phone]]></title><description><![CDATA[
<p>Article URL: <a href="https://github.com/phoneclaw/phoneclaw">https://github.com/phoneclaw/phoneclaw</a></p>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=47043279">https://news.ycombinator.com/item?id=47043279</a></p>
<p>Points: 3</p>
<p># Comments: 3</p>
]]></description><pubDate>Tue, 17 Feb 2026 03:13:49 +0000</pubDate><link>https://github.com/phoneclaw/phoneclaw</link><dc:creator>8dazo</dc:creator><comments>https://news.ycombinator.com/item?id=47043279</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47043279</guid></item></channel></rss>