<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: throw3954</title><link>https://news.ycombinator.com/user?id=throw3954</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Thu, 10 Sep 2026 14:55:15 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=throw3954" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by throw3954 in "GPT-6 Astra, looped transformers, and hidden reasoning"]]></title><description><![CDATA[
<p>It’s a little more complicated than that. While looped transformers can be unrolled a fixed number of times to save on memory, if loop depth is determined dynamically between tokens, a single transformer can compute any computable function between tokens.<p>To analogize, current transformers run a fixed-length program per step. Any program can be factored into a top-level loop with a fixed-length branching body (an interpreter). Dynamically looped transformers can run any program between tokens.<p>The safety argument for CoT monitoring is that in transformers information about the hidden state has to be communicated through the bottleneck of sampling a single token per forward pass. If not trained adversarially, it’s likely that a reasoning trace contains all the “bottlenecked information” we need to determine intent. But if we can compute arbitrary programs between tokens, the reasoning used is hidden.<p>It also opens the door to simple architectural extensions that would make the safety/monitoring side of things much more difficult.<p>It’s probably fine in practice at these scales though. If we keep each loop turn reasonable non-deep, we can probably recover most of the benefits by decoding “extended” CoTs from the residual stream at each loop turn between tokens. But that’s an area of active development.</p>
]]></description><pubDate>Wed, 09 Sep 2026 16:37:59 +0000</pubDate><link>https://news.ycombinator.com/item?id=49629289</link><dc:creator>throw3954</dc:creator><comments>https://news.ycombinator.com/item?id=49629289</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49629289</guid></item></channel></rss>