<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: alfablac</title><link>https://news.ycombinator.com/user?id=alfablac</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 23 Apr 2026 05:58:17 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=alfablac" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by alfablac in "Billing can be bypassed using a combo of subagents with an agent definition"]]></title><description><![CDATA[
<p>I'm the same person who commented on the issue in response to you lol.<p>I couldn’t reproduce this (even though I wanted it to work). That said, the fact that we can run sub-agents now (I've always used the default VS Code build and didn’t realize Insiders had a newer GHC Chat) already improves the experience a lot.<p>It’s pretty straightforward to set up an orchestrator that calls multiple sub-agents (all configured to use the same model on the first call) and have it loop through plan → implement → review → test indefinitely. When the context window hits its limit, it automatically summarizes the chat history and keeps going, until you finish the main agent’s plan. And that all costs a single Opus (or any other main chat model) request.</p>
]]></description><pubDate>Mon, 09 Feb 2026 18:41:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=46949072</link><dc:creator>alfablac</dc:creator><comments>https://news.ycombinator.com/item?id=46949072</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46949072</guid></item></channel></rss>