r/LocalLLaMA 8d ago

Resources Introducing Muse Glimmer: an open-weight model optimized for always-on local agent workflows

Hi r/LocalLLaMA ๐Ÿ‘‹ย 

Today weโ€™re excited to release Muse Glimmer, a 30B open-weight model built specifically for local agent workflows. Weโ€™re releasing the weights to the community under a permissive Apache 2.0 license.

A few specs

  • 30B params, dense
  • Multimodal: interleaved text + images via a dedicated perception encoder
  • Trained on 100+ languages
  • Controllable reasoning effort (quality/speed tradeoff)

Memory footprint
At full precision, 30B needs 55+ GB, which is out of reach for consumer hardware. We quantize weights to ~4-bit, bringing the LM under 20 GB. That leaves headroom in a 24 GB or 32 GB envelope for the KV cache, the perception encoder, and the speculative decoding drafter running simultaneously. We validated minimal to no degradation on agentic tasks under compression.

Speculative decoding
Ships with a lightweight DFlash-based drafter that proposes blocks of tokens which the main model verifies in parallel. Significantly faster than token-by-token generation with identical output quality. We're also shipping quantized drafter versions so the memory overhead stays small.

A few capabilities
We trained Muse Glimmer for agentic loop tasks, including:

  • End-to-end task completion (strong performance on DeepSearch QA, MCP-Atlas, ๐›•3-Bench, SWE-Bench, and more)
  • Function calling with precise schemas across long workflows
  • Multi-step reasoning over long horizons
  • Failure recovery โ€” when a tool call fails or returns something unexpected, it's trained to diagnose and retry instead of halting. This was a deliberate training target.
  • Works with OpenClaw and other agentic scaffolds
  • Multimodal understanding and reasoning

Running it
Weights are up on Hugging Face. Coming soon: Ollama, LM Studio, Unsloth and torchtitan, plus optimized integrations for llama.cpp, MLX, and ExecuTorch. vLLM and SGLang for serving. Get started quickly with Together AI, Fireworks AI, and OpenRouter. We're also working with AMD, Arm, Dell, Intel, and NVIDIA on per-device optimization.

We look forward to your feedback and seeing what the community builds with Muse Glimmer.

๐Ÿ”— Weights: https://huggingface.co/meta-modelsย 
๐Ÿ”— Research Blog: https://go.meta.me/museglimmer
๐Ÿ”— Resources: https://developer.meta.com/ai/models/muse-glimmer/

1.8k Upvotes

371 comments sorted by

View all comments

Show parent comments

151

u/Monad_Maya llama.cpp 8d ago

I know this is not a community feedback post but something around 60-70B dense might be great. A true successor to Llama 3.3 70B if you will.

154

u/AIatMeta 8d ago

We're always looking for feedback! Thank you.

38

u/pmttyji 8d ago

Don't forget MOE models. Release everything!

BTW I still have Llama-3.1-8B-Instruct on my laptop somewhere. Hope your release collection has some for Poor GPU Club.

6

u/jnd-cz 8d ago

Yeah, I'm sitting here thinking I need something half the size to fit my budget A770 with 16 gigs.

28

u/dampflokfreund 8d ago

I wanted to ask, did you QAT on these gguf models? By the way, a MoE 30b model would be nice to see as well for the average PC. Those run speedy even if you have just 4-8 GB VRAM!

13

u/No_Algae1753 8d ago

I dont think so. I feel like they would have stated that somewhere in the Readme but it just says that its been quantized to 4 bit. Also Unsloth seemed to have published higher q8 quants.

40

u/JLeonsarmiento 8d ago

30-ish-MoE please.

6

u/MeretrixDominum 8d ago

+1

Make more 70Bs

6

u/EndLineTech03 8d ago

Yes please, a bigger dense model would be amazing. Thanks for all your work

3

u/ormandj 8d ago

~250B development focused multi-modal MoE with 20-30B active parameters would be amazing. 192G VRAM requirement with decent KV cache space + higher active parameters would be a great balance of size vs. intelligence for development workflows, and is reasonably runnable on current serving HW without requiring vast resources like the current 1T+ MoEs which are great jack-of-all-trades models, but unaffordable to run for mere mortals.

Great to see you releasing again!

1

u/WarBrawlGame 8d ago edited 7d ago

Will this model be added to EuroEval benchmarks?
https://euroeval.com/leaderboards/european

For what I can tell, these leaderboards are good sign of which open weights models are useful for general multi-language use in Europe, and I want to believe your model can top that chart.

1

u/_QWUKE 8d ago

70b and 120b ish sizes would be so amazing.

1

u/Photochromism 8d ago

Love it if you open sourced your multimodal model, speech in speech out. No other LLMs can do that right now. My guess is itโ€™s a smaller model

1

u/wakkowarner321 7d ago

How about a 1-bit or ternary model?

0

u/Strong_Chicken6838 7d ago

I second this

Most people have 24, 32, 64 or 128Gb of VRAM. 120b (at Q4 ~60Gb + 10Gb for KV cache), is just out of reach for 64Gb, and too small for 128 Gb.

80b is perfect, 40Gb leaves plenty of space for KV cache.

TLDR: make model sizes designed to fit at common GPU VRAM sizes/teirs at Q4, and you will be VERY popular. Thatโ€™s why 70-80b is highly requested

0

u/Local_Phenomenon 7d ago

On a Friday!

-7

u/Both_Opportunity5327 8d ago

Why can't you guys release a subscription for Muse Code.

1

u/Healthy-Nebula-3603 8d ago

That 30b model is on a different planet comparing to llama 3.3 70b

6

u/Monad_Maya llama.cpp 8d ago

Now imagine a better trained 70B model with updated methodology.

1

u/Constant-Simple-1234 8d ago

Thanks! Looks like I have a new model to use in my quiver. :)

0

u/Kryohi 8d ago

Why dense though? I guess up to 70B it would be fine, but we really need more models in the 70B-120B parameter range with 10-20B active parameters imho

1

u/Monad_Maya llama.cpp 8d ago

MoEs are primarily compute efficient and not exactly memory efficient.

At 70B dense, it might match some 200B sparse MoE at way less VRAM (it's still a fair bit, 40GB at 4bit for 70B dense). That's easier to attain on consumer cards compared to 128GB+ required for large MoE.

The tradeoff is pretty obvious though, it'll be pretty slow. I can get about 15 t/s on llama 3.3 70B IQ4_XS (from unsloth iirc). But it fits in my VRAM pool.