ML/AI research engineer. Ex stats professor. Author of "Build a Large Language Model From Scratch" (https://t.co/O8LAAMRzzW) & reasoning (https://t.co/5TueQKx2Fk)
Inkling 2 Small took a while... but it's more interesting than I initially thought! Using attention residuals (like Kimi K3), but without the linear-attention hybrid. Food for discussion for the end-of-the-year architecture trends analysis!
Seb's Law, co-signed by another Seb
Seb's Law: The widespread, transformative societal impact of AI is always approximately two years away, regardless of the current year.
View quoted postWow that escalated quickly. Was gone for a few weeks and now pretty much everyone launched their own decision model copycats: - Sep 23: Together AI, Tev1-4B - Sep 24: Alibaba Cloud, decision-model - Sep 29: Liquid AI, d1 - Sep 30: Databricks, ai_decide - Oct 1: Amazon AWS, Strands Decider 2B - Oct 1: Cloudflare, Clef and Clef-flash (Clef-omni on Oct 9) - Oct 1: Perplexity, Decider (v1.3 on Nov 12) - Oct 6: OpenAI, Decisions API (GPT-6 Luna) - Oct 7: http://H2O.ai, H2O-Lightning-4B - Oct 7: Snowflake, Snowflake Decision - Oct 9: Microsoft, Microsoft-Decision-1 - Oct 15: IBM, Granite Switch 4.1 with Decision adapter - Oct 21: Baseten, Mammoth-1 and Elephant-1 - Nov 6: Salesforce, Koa Decisions - Nov 11: Google DeepMind, Gemini Decision 1 According to a Vercel report, 26% of requests are now routed through decision models ๐
Took a while, but here it is, a mega write-up on language models for text classification and, of course, Jev. It's basically a visual guide to RNNs, CNNs, transformers, and calibration, with hands-on experiments on accuracy and efficiency.
Hoping Nemotron keeps going. Thankfully, open weight LLMs have some alternatives. But their open data and full training recipes would be much harder to replace.
LLM training is hard. Hard to be a jack of all trades.
im surprised there isnt more pretrain-postrain codesign i guess companies really do ship their org charts
View quoted postIn reasoning model development, it's always been this interesting tension between training/optimizing chain-of-thoughts (CoTs) vs not touching them to preserve monitorability. CoTs are cool because we can check what the model is up to (e.g., whether it cheats or not) as long as it spells out its thought process. And we risk losing that if we explicitly optimize CoTs. Two caveats: 1) I.e., the catch of CoT and monitorability is that this only works if the written thinking reflects what the model is actually doing. 2) Also, when models become more capable, they spell out less in the CoT (like a cleverer math student needs less note-taking when solving problems during an exam). Nothing new on that front, but an interesting thread below on how to measure "harder to monitor", with some interesting results that confirm the existing intuitions: 1) no-CoT capability (meaning how much reasoning the model can do in a single forward pass without writing anything down) - Better pretraining (lower perplexity) raises this no-CoT capability - Architecture mostly doesn't matter 2) CoT controllability (meaning how well the model can change its written reasoning when asked to add, remove, or change parts of it) - RL alone raises controllability a lot - Controllability is passed on through distillation * Higher no-CoT capability and higher controllability both make monitoring harder. PS: Perhaps the good news is that it seems that process supervision wasn't the main culprit.
(1/10) Today, weโre sharing new research from @OpenAI: How does CoT monitorability (no-CoT capability and CoT controllability) evolve over the model training lifecycle? We emerged with unsurprising but sobering findings: as we scale toward more intelligent systems, models are
RTโBrian i've never learned as much as when building things from scratch. currently working through build a large language model by @rasbt, and it's one of the best ways i've found to actually understand how llms work. still struggling to visualize all those dimensions.
Hillclimbing: Make the model better (best intentions). Benchmarking: Measure how much better (best effort). Benchmaxxing: Make the numbers look better (best optics).
We gotta have a conversation about hill climbing vs benchmarking vs benchmaxxing
View quoted postHow open-weight LLMs are shifting from full attention to hybrid and sparse designs, and what that means for long-context compute and memory.
Currently working towards a bigger open LLM roundup. But in the meantime, just one of the interesting trends that stood out. I.e., looks like the transition from full to hybrid attention continues. In 2025, there were still lots of full attention models, with a shift to "some full attention" hybrids. In the first half of 2026, the trend towards "some full attention" hybrids continued. And now, in the second half of 2026, we have a 50/50 split between "some full attention" hybrids and models that don't use full attention at all anymore. And yes, there are also no full attention models anymore. The plot legend here means, - Full attention throughout = Global MHA, GQA, dense MLA, CCA in EVERY layer. - Some full attention = Full global attn mixed with: sliding-window/chunked attention, Gated DeltaNet, KDA, Mamba-2, Lightning Attention, convolutions, sparse attention. - No full attention = Zero dense global layers. The main implication is that the trend goes towards making long contexts cheaper to use. This means, it makes the architectures more suitable for long documents and conversations, large code bases, and of course agent usecases that rely on a lot of tool calls. In particular, there are two distinct efficiency gains here: 1) Less attention computation, since sparse attention and the like select tokens or blocks from the context and performs the expensive attention operation from only that subset. (Note that it can still retrieve information from distant positions.) 2) Less memory for retaining context in some architectures, meaning that recurrent layers such as Gated DeltaNet maintain a fixed-size state. Of course, this saves memory, but compressing the history creates challenges for exact retrieval, so they are usually intermixed with traditional attention methods (sparse or full).
Activity on rasbt/LLMs-from-scratch
rasbt closed an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/llm-architecture-gallery
rasbt contributed to rasbt/llm-architecture-gallery
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt contributed to rasbt/LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt closed an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt commented on an issue in LLMs-from-scratch
View on GitHubWhat could possibly go wrong?
We asked GPT-6 Astra to edit Qwen3.5-0.8B weights to improve math. It directly changed only 0.016% of weights, fixing 0.8B's reasoning loops & improving math up to 6x and even instruction following 3x, without gradients or training. We call this Weight-Space Programming:
Activity on rasbt/reasoning-from-scratch
rasbt closed an issue in reasoning-from-scratch
View on GitHubActivity on rasbt/reasoning-from-scratch
rasbt opened a pull request in reasoning-from-scratch
View on GitHubActivity on rasbt/llm-architecture-gallery
rasbt closed an issue in llm-architecture-gallery
View on GitHubActivity on rasbt/llm-architecture-gallery
rasbt contributed to rasbt/llm-architecture-gallery
View on GitHubActivity on rasbt/llm-architecture-gallery
rasbt commented on an issue in llm-architecture-gallery
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt closed an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt closed an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt commented on an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubThe complete reasoning-from-scratch video series is now up (and linked) here: https://magazine.sebastianraschka.com/p/building-reasoning-models (Taking a short break but will be back with LLM model and research updates in November!)
Spontaneous morning chat with Juergen Schmidhuber and Jake Newfield philosophizing about AI. Sry my mic somehow disconnected but Juergen had the more interesting points anyways!
Our CEO @Jake_Newfield brought together @SchmidhuberAI ("father of AI" and pioneer of deep learning) and @rasbt (author of Build a Large Language Model), to discuss humanityโs future with AI: https://www.youtube.com/watch?v=fcOTx06qYtQ
Activity on rasbt/llm-architecture-gallery
rasbt contributed to rasbt/llm-architecture-gallery
View on GitHubActivity on repository
rasbt pushed reasoning-from-scratch
View on GitHubActivity on rasbt/reasoning-from-scratch
rasbt opened a pull request in reasoning-from-scratch
View on GitHubActivity on repository
rasbt pushed reasoning-from-scratch
View on GitHubActivity on rasbt/reasoning-from-scratch
rasbt opened a pull request in reasoning-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt commented on an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt closed an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt commented on an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt closed an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt commented on an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt assigned an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt commented on an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/reasoning-from-scratch
rasbt opened a pull request in reasoning-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt closed a pull request in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubActivity on rasbt/reasoning-from-scratch
rasbt opened a pull request in reasoning-from-scratch
View on GitHubActivity on rasbt/reasoning-from-scratch
rasbt opened a pull request in reasoning-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt commented on an issue in LLMs-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubActivity on rasbt/mlxtend
rasbt closed an issue in mlxtend
View on GitHubRTโSebastian Raschka Re Update: OpenAI just added a Jev clone ๐
Activity on rasbt/mlxtend
rasbt commented on an issue in mlxtend
View on GitHubActivity on rasbt/mlxtend
rasbt closed an issue in mlxtend
View on GitHubActivity on rasbt/mlxtend
rasbt commented on an issue in mlxtend
View on GitHubActivity on rasbt/mlxtend
rasbt closed an issue in mlxtend
View on GitHubActivity on rasbt/mlxtend
rasbt contributed to rasbt/mlxtend
View on GitHubActivity on rasbt/mlxtend
rasbt closed an issue in mlxtend
View on GitHubWhy I'd invest in post-training existing open-weight LLMs, with Fireworks' Ember-1 as an example of more token-efficient reasoning.
A little Ember-1 tl;dr. Seems like a great model! (Was recently asked on a podcast, given $ xx million, what's the best way to develop a frontier LLM today? My recommendation was: start with an existing one and spend that budget on post-training. Great example here.)
Ember-1 is hot on HN, our research team cooked itโs Kimi K3 post trained to be 40% more concise in reasoning same quality, 40% faster and cheaper
Activity on repository
rasbt pushed llm-architecture-gallery
View on GitHubActivity on rasbt/llm-architecture-gallery
rasbt contributed to rasbt/llm-architecture-gallery
View on GitHubActivity on repository
rasbt pushed deeplearning-models
View on GitHubActivity on rasbt/mlxtend
rasbt closed an issue in mlxtend
View on GitHubActivity on rasbt/mlxtend
rasbt closed an issue in mlxtend
View on GitHubActivity on rasbt/mlxtend
rasbt closed an issue in mlxtend
View on GitHubActivity on repository
rasbt pushed reasoning-from-scratch
View on GitHubActivity on rasbt/reasoning-from-scratch
rasbt commented on pull request rasbt/reasoning-from-scratch#269
View on GitHubThe main appeal of open-source agent harnesses isn't that they are free, but that we can inspect what they are doing on our computers.
Notes on MiMo-V2.6 Pro's GQA and sliding-window attention, agent training tasks, reward signals, and large RL batches.
MiMo-V2.6 is "simply" the best (for now). Despite its simple architecture design it's currently No.1 in the open-weight benchmarks (weighted average). With "simple," I mean a classic Grouped Query Attention (GQA) with Sliding Window Attention (SWA) at a tiny 128-token window size. So, that underlines one of the points I've been trying to make in recent months: most of the progress still comes from the data and post-training recipe improvements. Fancy attention variants are just mostly efficiency tweaks. What are some of the training data improvements and recipe improvements? The MiMo team shared a pretty detailed technical report. Lots to carefully digest there, but in short, there are a few things that stood out: 1. An increase in agent tasks; also training across different harnesses (the average DeepSWE pass@1 accuracy on held-out harnesses improved from approximately 50% -> 66%). 2. Better reward signals: they replaced a simple correctness verifier with an agentic grader that looks at the execution traces as well. 3. Large RL batches (1,568 prompts ร 16 rollouts = 25,088 trajectories) and 2.7โ3.7 billion training tokens per update (unclear, though, what the predecessor used).
MiMo-V2.6-Pro debuts as the top open weights model on the Artificial Analysis Intelligence Index (46). At $0.13 per Intelligence Index task, it lands on the Intelligence vs. Cost per Task Pareto frontier @Xiaomi has just released MiMo-V2.6-Pro, an open weights model with major
A short note on Jev's generalization, possible encoder-style architecture and training, and Choice and Noul API examples.
Itโs easy to dismiss Jev it as โjust a classifierโ. But people (me included) who have been training encoder-style models for classification for many years know they were usually special-purpose and limited in some way. The breakthrough of Jev is that it generalizes well. And Iโd say the secret sauce is probably more in the data than in the training algorithm. (Plus a nice API design on top of it.)
poor guy claim to have built Jev a year ago but no one cared, and now Jev stole all the thunder many people are saying โyou gotta tell your storyโ or โmarketing is importantโ, and they just completely missed what actually made the difference here i just looked into this laya
Interesting new insights into the old AdamW vs Muon debate: Muon seems to do better because it reduces memorization.
๐๐ฑ๐ฎ๐บ๐ช ๐๐. ๐ ๐๐ผ๐ป: ฮฑ, ๐ข๐๐ฒ๐ฟ๐ณ๐ถ๐๐๐ถ๐ป๐ด, ๐ฎ๐ป๐ฑ ๐ ๐ฒ๐บ๐ผ๐ฟ๐ถ๐๐ฎ๐๐ถ๐ผ๐ป. A quick update on our WeightWatcher experiments comparing AdamW with the newer Muon optimizer. We trained a single-head nanoGPT model with both optimizers across five seeds. We then used
Activity on repository
rasbt pushed reasoning-from-scratch
View on GitHubActivity on rasbt/reasoning-from-scratch
rasbt opened a pull request in reasoning-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHubActivity on repository
rasbt pushed reasoning-from-scratch
View on GitHubActivity on rasbt/LLMs-from-scratch
rasbt opened a pull request in LLMs-from-scratch
View on GitHub