Frontier labs are rumored to be adopting looped Transformers for their potential to unlock implicit reasoning. But can looped Transformers really master it?
We find a bottleneck that keeps looped Transformers from perfect implicit reasoning. Using mechanistic interpretability, we show how looping helps implicit reasoning, why it still struggles to generalize, and how to fix it.
We introduce DiscoLoop: a residual design for looped Transformers that improves implicit reasoning.
๐งต Long thread ahead ๐
Frontier labs are rumored to be adopting looped Transformers for their potential to unlock implicit reasoning. But can looped Transformers really master it?
We find a bottleneck that keeps looped Transformers from perfect implicit reasoning. Using mechanistic interpretability, we show how looping helps implicit reasoning, why it still struggles to generalize, and how to fix it.
We introduce DiscoLoop: a residual design for looped Transformers that improves implicit reasoning.
๐งต Long thread ahead ๐
Thank you! These are really good questions.
We did try feeding only the decoded embeddings into the next loop during training, but optimization broke down and the model did not generalize well. Our hypothesis is that keeping the continuous state mainly helps optimization and carries contextual information from the input (e.g., the relation). The continuous channel leaves a smooth path through the recurrence, so gradients can flow across loops without being routed entirely through the decode-then-encode operator.
We haven't tried changing the size ratio between graph A and graph B (or adding more A-like graphs) yet, but it's definitely worth trying!
Frontier labs are rumored to be adopting looped Transformers for their potential to unlock implicit reasoning. But can looped Transformers really master it?
We find a bottleneck that keeps looped Transformers from perfect implicit reasoning. Using mechanistic interpretability, we show how looping helps implicit reasoning, why it still struggles to generalize, and how to fix it.
We introduce DiscoLoop: a residual design for looped Transformers that improves implicit reasoning.
๐งต Long thread ahead ๐
@SreeramG Thanks! It's a soft, learned mix rather than a hard swap from hidden states to embeddings. The design principle is that later loops should get inputs the model knows how to read. Better ways to close the mismatch are very open!
For simplicity we used a fixed number of loops during training. But Discoloop is completely compatible with adaptive looping! In multi-hop tasks, we find that looping more than the required reasoning depth can even refine the accuracy!
Figure below shows a looped model trained on multi-hop questions with at most 5 hops. At test time, looping more than 5 times raises the OOD accuracy significantly.
Thanks for your advice! We chose full layer loop to ablate the โlocal-depth storageโ issue in the multi-hop reasoning tasks, but it is completely worth trying middle layer loop! This also reminds me of a fantastic blog comparing full layer loop and middle layer loop in real pretraining https://t.co/DCxvYsNs8S
@arundsharma@latentpedia Thank you! This is a very interesting perspective! For knowledge retrieval, it makes perfect sense to use outer structures system like RAG and build a graph for direct retrieval of the multihop answer!
Thank you! That's exactly why mechanistic interpretability matters: it lets us read an LLM's hidden thoughts. Looping is interesting here too. In real language modeling, it may not just add reasoning depth. It may also refine the looped tokens as they settle toward a fixed point.