alt Hacker NewsMeta Muse Glimmer – open weights 30B local coding model
Comments
Will be interesting to see how Qwen3.8 27B compares against this once it releases this week. Seems like dense 30B is back in fashion?
EDIT: An open weight version of Muse Spark 1.2 is going to be released as well:
https://x.com/alexandr_wang/status/2086756152034066792
https://xcancel.com/alexandr_wang/status/2086756152034066792
Three of these landed in the same week. Mistral's Shieldstral is a 3B safety classifier that matches models 7x its size, and Google shipped Gemma Translator which runs entirely offline. Different problems, same shape. Small open weights, local, no API call.
With the business model for API based LLMs looking iffy at best it seems like we’re heading back to the “server under your desk” era of IT again.
Some interesting findings from the chat template designs:
1. The template name is Onyx ATEM as found in the tool call exception message
2. It appears to be following a harmony-style chat template. But the tool use seems to be a xml like :<atem:function_calls> / <atem:invoke> / <atem:parameter>
3. atem: a internal joke of meta in reverse?
https://huggingface.co/meta-models/Muse-Glimmer-30B/blob/mai...
That's a bit amusing - not that I have the hardware to run it, but officially it's not available in Hong Kong. Not that getting it would be much of a problem with a help of a VPN either, but I'll assume mainland China is also restricted. Certainly not a competition for Chinese open weight models... in China.
It is interesting but it does look like a careful distillation of (Spark and) biggers open-weight models.
The progress compared to Qwen3.6 27B is good, not that impressive, it's a 4 months old model. (kuto to them to compare to 27B dense and not 35B MoE, it's more fair to do so). It is very probable that Qwen3.8 27B will crush Glimmer-30B on most benchmarks.
The comparison set is Gemma4-31B and Qwen3.6-27B, not the current Qwen
Fair on size, but the headline numbers are against a model a generation back
Still needs 32-64GB memory to run it locally. 64GB Macbook pro with an M5 chip costs more than 4k Euros in Germany. A more practical model would be a language specific (e.g Python or JVM language) and excellent at tool calling and reasoning. Maybe that way they can shrink it even more.
What I think would be perfect is a model that could run on a single DGX spark and be competitive with DSV4 Flash 731. Flash is already a game changer. Hopefully meta plans on this, like the old 70b. V4 flash is smart enough for any use but slightly too big. 27b-30b isn’t intelligent enough.
Optimizing speed is really the way to go. Yet 24GB is not what everyone can afford. Maybe we could take some of those 56tk/s and transfer into some free RAM space using MoE loading ? I'd be glad with a less than 10GB and more than 6tk/s model.
Great to see Meta back, looks like really strong, local model, can't wait for llama.cpp support.
How are you handling the tradeoff between quantization for device fit and accuracy loss on tool calling? That's where local agents typically break down in production.
Where is the pelican??
Looking forward to giving this a try with llama.cpp. I’m watching the open-weights competition with high expectations.
Another candidate for the 7900XT (20GB VRAM) I got sitting around. I pulled latest llama.cpp (targeting vulkan during build) after seeing a muse PR merged a few hours ago, and unsloth/Muse-Glimmer-30B-GGUF:UD-Q4_K_XL runs on my 7900XT barely (and with no MTP). Sits at 19GB VRAM w/ 4 parallel 113k context slots, all layers on GPU, and at 700 tok/s prompt, and ~36 tok/s generation.
Waiting on Q3 to download to check speed + do my usual anecdotes. I generate beefy code snippets and poems, and also ingest my HOA declaration and answer nuanced questions.
edit: i should've prefaced this somewhere with: This card ballparks at 800GB/s IO, which I can't seem to find easily on the market anymore. Kinda the ideal card for this model, if I just had a _little_ more VRAM (XTX is 24GB).
Meta seems like the one American bigtech that would distill the the other American frontier models. My enemy’s enemy is my friend?
Meta released their own 4-bit quant of this model for devices with 24GB VRAM.
That's a modern gaming laptop; cheapest I see in the US with 24GB is $3.5k.
Should be quite a bit faster than the new M5 MacBook Pro, and you can run Linux on it!
Meta did not abandon opensource. I would love to see a smaller distill, or a moe of this size but the benchmarks seems competetive as long as it isnt benchmaxed witch i would not be suprosed if it is.
The favourable comparisons to Gemma 4 and qwen3.6 look promising!
I wish they would release the quantized versions in a safetensor format. Many frameworks can't load PTE and GGUF.
Meta knows how to win back developer's hearts .... let's see if they have the goods
The more open weight models get released the greater the market for personal and small business oriented hardware to run these models. This will drive lower cost hardware, which has stagnated in recent years due to most software not needing the performance and capacity.
Wow, Meta is back (at least for now)!
I like this class of model. Multi-token prediction makes it viable to run dense models at not-too-far-off speeds as MoE models with much better intelligence.
The submission’s title (open weights 30B local coding model) is luckily wrong: This is meant to be a general agentic model.
It even comes pre-quantized and with a MTP/drafter model. Looking good!
Let’s hope they aren’t dishonest with the benchmarks this time …
[flagged]
[flagged]
"Meta Muse" immediately made me think of Metamucil.
Product teams really need to hire at least one or two people with a 12-year-old's sense is humor. They need to winnow all the potential stupid jokes out of their product namings.
As an industry, I wish we would stop calling these things "open weight" because it is too easy to confuse with actual "open source", which they are not.
Photoshop source code+ OSI license = open source
Photoshop binary you can run on your own computer = open weight
Photoshop SaaS web app = closed, proprietary (Opus, GPT, etc.)
"Open weight" models are still just binary blobs that are completely inscrutable. It's like bringing home a dog from the rescue and just hoping that it doesn't have a tendency to bite kids in the face. You just can't know. The only thing that you can do is try to add more training (fine tuning) telling it not to bite kids.
I don't think the FOSS community has ever accepted this, but somehow we're feeling like it is okay now.
I lament the comments saying this in any way redeems Meta (the company).
The researchers releasing this stuff have almost nothing to do with Meta other than being bankrolled by the slaughterhouse.
You aren't the customer, you are the pawn in big tech's game of thrones. Your good will is a commodity to be traded, almost literally. It will be used against you the moment it's convenient. This is open weights because Meta couldn't monetize it in any other way than to cloud developer's judgement of their reputation.
But I guess most people just don't care.
I'm glad it's open. It does not make me think any better of Meta.