Intriguing. Should be interesting to compare this to Qwen3.8 (27B). I've been plenty impressed with Qwen's ability, but boy does it like to overthink things, even after getting it off the default xhigh reasoning, it'll take 20 minutes to plan something, thinking so much it'll have to compress its context multiple times to reach a single answer. The quality of the answer is great, but there has to be a middle ground.
post
We are releasing intermediate checkpoints, training data or detailed data-construction recipes
👀
Is this the first actually open source model?
Can't wait for it to hit ollama so I can easily add it into my flow. I really need a better ollama alternative where I can easily download, manage, and run gguf locally and tie it in with opencode, zed, and open-webui
A word of advice, consider switching to something else.
Llama.cpp of course! After I did the switch, never looked back. Add llama-swap in front of you switch between models often.
llama-server has router mode built-in; you don't need separate software to swap models. I keep a list of my models in a presets.ini file.
Yes but llama server does not unload models to fit a different model. At least, didn't managed to have just llama.cpp swap between models that fill up my vram... The second one would fail load.
Ah. I POST to '/models/unload' when I switch models as part of my tooling -- if llama-swap is doing that for you, then I get why you'd want it.
Yes, llama swap also give you a pretty web based statistics of all the calls and runs for every model with t/s and more statistics.
It's pretty neat... You can also load and unload models manually, define groups for models that fit together in vram and so on.
It gives you that automation that people coming from ollama are used to.
under the hood all it does is running llama serve. You convert your models.ini to a yaml file 1:1 (plus a few more flexibility).
all 16 comments