MiMo-V2.6: The Hard Road to Scaling Up RL
MiMo-V2.6 is very likely one of the largest single RL runs, by compute, that any open-source model team has undertaken to date. In an era when compute is brutally scarce, we still chose to dedicate a team of several dozen people to one goal over an extended period: scaling up RL. That takes more than research conviction. It takes a vision for AGI, respect for the unknown, and the nerve to walk straight into the hardest problems.
The result is a model whose potential was built through mid-training and unlocked through heavy RL. Today, it is the number one open-source model. I strongly recommend reading the technical report. I believe it will become one of those papers that Agent RL practitioners keep reopening and discovering something new in each time. In my view, the research innovations and engineering challenges behind it surpass those of DeepSeek R1, which I was partly involved in.
Some will ask: why MixRL instead of MOPD? First, they are not competing choices. We ran MixRL on verifiable tasks of moderate difficulty, including code and related agentic tasks, and found that the resulting models generalize remarkably well. Second, tasks that are difficult to verify, extremely long-horizon, or simply too challenging to include in a joint RL run are trained separately. Including them would substantially reduce rollout efficiency or introduce significant rollout staleness. We then merge the resulting capabilities through MOPD. Games, 3D tasks, and tasks with subjective evaluation signals all fall into this category.
There is also a third, slightly cheeky answer. Our team is flat enough and free enough of organizational silos that MixRL simply is not difficult for us. More importantly, everyone enjoys working this way. People from different domains come together every day, driven by the pursuit of AGI and intelligence that can continuously improve itself, to confront and resolve the RL bottlenecks in each field. I will always remember the RL daily update meetings from this period. They were intense and dense, with intelligence emerging in real time.
To help the open-source community focus on solving real Agentic RL problems, we have released a Qwen model distilled from MiMo RL trajectories as a stronger starting point for RL, along with 7K diverse environments and a complete RL training framework. We hope these resources will help move Agentic RL research forward.
MiMo-V2.6 is only the beginning. In an era when intelligence is easy to replicate, we still choose the hard road toward self-improvement and AGI. Much of what lies ahead remains unknown. But we are willing to keep investing the time, compute, and passion required to take on one hard problem after another and work each of them all the way through, until intelligence crosses into a new regime.
After spending so much time working with agents, I often feel a little disoriented. I’ve built so much. But how much have I actually learned?
Over the past three years, LLMs and agents have gone from something like an eight-year-old to an Olympiad gold medalist. Agent harnesses are everywhere. But much less attention seems to go toward human growth. How can AI help us understand the world better?
So I built Shan, a Shared Human–Agent Notebook.
It started with a thought: what if I could put all my ideas into a box, and the box could organize them for me?
With one rule: leave what I wrote intact. Be quiet. Help through comments, or other ways that give me room to think.
Let it handle the things my brain struggles with. Remind me what I was working on two years ago. Research, in parallel, the ten ideas that popped into my head while I was on the toilet. And a lot more.
And I want to own my notes. GitHub works. I want every note to be a Git commit, and I want to be able to git clone the whole notebook.
As it happens, Tibo gave me more Astra tokens than I know what to do with. So naturally, Shan also connects to my Codex subscription and helps me burn through all those unused resets.
All of this is built. Shan is now in early beta.
Link in the reply. Hope you like it.
I’d love to see Amp add a feature that automatically renames a thread every three turns.
The goal of a task can evolve as the conversation progresses, which can make it quite difficult to find previous tasks later on.
Alternatively, it would be great if Amp could provide a rename thread Plugin API so we could implement small features like this ourselves.
Thanks!
@amp