Kusha Sareen

111 posts

Kusha Sareen banner
Kusha Sareen

Kusha Sareen

@KushaSareen

learning continually @Mila_Quebec / @mcgillu !

Montreal, QC Katılım Eylül 2024
239 Takip Edilen465 Takipçiler
Sabitlenmiş Tweet
Kusha Sareen
Kusha Sareen@KushaSareen·
Can LLMs adapt continually without losing base skills? Fast-Slow Training (FST) pairs "slow" weights with "fast" context. FST vs. RL: • 3x more sample-efficient • Higher performance ceiling • Less KL drift (better plasticity) • Continual learning: succeeds where RL stalls
Kusha Sareen tweet media
English
20
92
542
130.1K
Dan McAteer
Dan McAteer@daniel_mac8·
babe, wake up. new continual learning breakthrough just dropped. fast-slow training (fst) treats model params as "slow" weights and optimized context as "fast weights". "across math, code, and general reasoning benchmarks, fst beats weights-only training on *every* axis we measured."
Dan McAteer tweet media
English
20
91
786
41.8K
Kusha Sareen
Kusha Sareen@KushaSareen·
It generally seems to depend on the dataset/model and also how much budget you allow for GEPA (you can get the model to rely more/less on the prompt depending on how much information you allow into it), so there are some knobs here you could use to control this. Importantly, the whole point of the paper is that, in a continual learning setup, not all domain-specific information needs to go into the model weights. We're planning on running some more evals related to this.
Kusha Sareen tweet media
English
0
1
12
661
Kusha Sareen
Kusha Sareen@KushaSareen·
Can LLMs adapt continually without losing base skills? Fast-Slow Training (FST) pairs "slow" weights with "fast" context. FST vs. RL: • 3x more sample-efficient • Higher performance ceiling • Less KL drift (better plasticity) • Continual learning: succeeds where RL stalls
Kusha Sareen tweet media
English
20
92
542
130.1K
Kusha Sareen
Kusha Sareen@KushaSareen·
Hey! That's a great question and we thought about it a bit. For simplicity, we just kept the GEPA prompt that had the highest validation accuracy but there are certainly other options! Eg. what we get from this algorithm is really (pool of prompts, model) rather than just (prompt, model) so there are all kinds of clever things you could do to better make use of the pool of prompts at inference time.
English
2
1
11
1K
Kusha Sareen retweetledi
Rishabh Agarwal
Rishabh Agarwal@agarwl_·
GPT-3 was a sensation because it claimed language models are few-shot in-context learners. I wonder why we dropped the ball on in-context learning, and moved to mostly execution oriented research on LLMs: training on any task of high value, a set that will keep increasing with no end in sight. Maybe we'll get these data centers with geniuses, but they are *only* geniuses on tasks that your favourite frontier lab decides to directly / indirectly optimize for.
Delip Rao e/σ@deliprao

In-context learning in LLMs

English
15
13
190
29.9K
Kusha Sareen retweetledi
Rishabh Tiwari
Rishabh Tiwari@rish2k1·
Thanks for sharing, I agree with the motivations and ideas you mentioned, for better understanding it can be seen as FST instantiation where: *slow weights* update rule = self distillation *fast weights* update rule = GEPA we did try one experiment in the same spirit in which we distilled FST fast-weights (gepa style prompt) back to the model using on-policy reverse KL (similar to SDFT paper) and leads to some learning but performs worse than FST w/ GEPA+RL (@LakshyAAAgrawal explained this result in more detail here: x.com/LakshyAAAgrawa…). The idea of combining RLVR signal with self distillation signal is also very interesting and we did try that as well some time back in a related project, we are planning to release that as well soon.
Rishabh Tiwari tweet media
English
2
3
10
861
Kusha Sareen retweetledi
Devvrit
Devvrit@Devvrit_Khatri·
ICL lets models adapt rapidly to changing tasks (✅), but the weights stay frozen - leaving performance gains on the table (⚠️). Fine-tuning (like SFT, RL) reaches a higher perf ceiling (✅), but is slow, can hurt OOD performance, and often reduces plasticity (⚠️). Why not combine the strengths (✅) of both? We introduce Fast-Slow Training (FST): fast weights (prompts) quickly capture task-specific nuances, while slow weights (model parameters) internalize the more general, task-agnostic reasoning patterns that should persist across tasks. FST reaches a higher perf asymptote while being more efficient. Since prompts absorb more of the task-specific information, the parameters do not need to move as much. As a result, the model stays closer to the base model, and preserves more plasticity for learning new tasks!
Rishabh Agarwal@agarwl_

Training LLMs is synonymous with updating their weights. However, LLMs can also learn in-context using *frozen* weights. There is no good reason for restricting learning to being in-context or in-weights. So a natural idea is "Learning, Fast and Slow" (FST). In FST, slow learning is LLM weights trained with RL while fast learning is context / prompt (fast weights) optimized with GEPA. Compared to RL, FST performs better while being more data efficient, adaptable (plasticity), and forgetting less (stays closer to base models). I think this idea of learning both fast-slow weights would be a good foundation for continual learning. PS: Geoff Hinton (the OG) described the idea of fast weights and slow weights several years ago, and back then I remember thinking it's a very cool idea. See more details here: gepa-ai.github.io/gepa/blog/2026…

English
1
14
51
12.6K
Kusha Sareen retweetledi
Kusha Sareen retweetledi
Rishabh Agarwal
Rishabh Agarwal@agarwl_·
Training LLMs is synonymous with updating their weights. However, LLMs can also learn in-context using *frozen* weights. There is no good reason for restricting learning to being in-context or in-weights. So a natural idea is "Learning, Fast and Slow" (FST). In FST, slow learning is LLM weights trained with RL while fast learning is context / prompt (fast weights) optimized with GEPA. Compared to RL, FST performs better while being more data efficient, adaptable (plasticity), and forgetting less (stays closer to base models). I think this idea of learning both fast-slow weights would be a good foundation for continual learning. PS: Geoff Hinton (the OG) described the idea of fast weights and slow weights several years ago, and back then I remember thinking it's a very cool idea. See more details here: gepa-ai.github.io/gepa/blog/2026…
Rishabh Agarwal tweet media
English
18
73
566
69.4K
Kusha Sareen retweetledi
Moksh Jain
Moksh Jain@JainMoksh·
The scientific process involves collecting informative measurements while effectively allocating limited resources. We developed MaD-Physics, a new benchmark to measure this capability of agents.
English
1
17
38
6.1K
Kusha Sareen retweetledi
Rishabh Tiwari
Rishabh Tiwari@rish2k1·
Great article, I see a future where learning algorithms will co-evolve model-parameters and harness around around it for continuous improvement. Just like prompt engineering is better handled by a principled algorithm like GEPA, soon harness engineering will be handled by class of algorithms like FST (fast-slow training). x.com/KushaSareen/st…
English
1
2
13
1K
Kusha Sareen retweetledi
Kusha Sareen retweetledi
Lakshya A Agrawal
Lakshya A Agrawal@LakshyAAAgrawal·
Learning from rich textual feedback (errors, traces, partial reasoning) beats scalar reward alone for LLM optimization. GEPA demonstrated this for context-space optimization (prompts and agent harnesses), delivering frontier results at a fraction of the cost of RL. But context-only optimization is bounded by the base model's capability ceiling; weight updates can reach further. Very excited about this new line of work on Fast-Slow Training (FST), which interleaves context and model weight optimization! The idea is a clean division of labor between two interleaved loops: 🔹 Fast loop (context): GEPA reads rich rollout feedback updating the context layer. The context becomes a fast-updating scratchpad of what the model needs to know about this task, right now. 🔹 Slow loop (model parameters): RL updates the model's parameters conditioned on the evolving context. Because the prompt already carries task-specific nuances, the model parameters are freed from absorbing them and focus on what actually generalizes across tasks and pushes the frontier. ⦁ 3× more sample-efficient than RL on math, code, and physics reasoning ⦁ ~70% lower KL divergence from base at matched accuracy ⦁ Plasticity preserved: FST checkpoints respond better to additional RL on new tasks than RL-only ones ⦁ Continual learning across changing tasks (HoVer → CodeIO → Physics) where RL stalls the moment the task switches FST is a direction towards: ⦁ Addressing RL's pain points: entropy collapse, sparse rewards, long-horizon exploration ⦁ Providing a clean channel for rich feedback into weight updates ⦁ Demonstrating model-harness co-evolution ⦁ Discovery: Using fast context updates for broad exploration, while leveraging a continually improving model. Check out the full thread below:
Kusha Sareen@KushaSareen

Can LLMs adapt continually without losing base skills? Fast-Slow Training (FST) pairs "slow" weights with "fast" context. FST vs. RL: • 3x more sample-efficient • Higher performance ceiling • Less KL drift (better plasticity) • Continual learning: succeeds where RL stalls

English
13
43
186
33K
Kusha Sareen retweetledi
Kusha Sareen retweetledi
Kusha Sareen
Kusha Sareen@KushaSareen·
More broadly, FST represents a general blueprint for continual learning in LLMs: optimize context (using any method) to quickly learn task-specific information and update parameters (using any method) to build a general reasoning core. Incredibly grateful to the wonderful team: @rish2k1 @LakshyAAAgrawal @profjoeyg @matei_zaharia @KurtKeutzer @inderjit_ml @agarwl_ @Devvrit_Khatri Blog: gepa-ai.github.io/gepa/blog/2026… Paper: arxiv.org/abs/2605.12484 Code: rishabhtiwari.ai/projects/fst/c…
English
1
6
25
2.7K
Kusha Sareen
Kusha Sareen@KushaSareen·
The KL trajectories help understand why FST mitigates plasticity loss. Standard RL forces models to heavily update their weights to maximize reward, which drives up KL wrt the base model. Since FST offloads task-specific details to the prompt, the core model parameters don't need to shift nearly as much. We see higher performance with significantly less deviation from the base model.
Kusha Sareen tweet media
English
1
4
15
2.7K