Meta just shipped two Muse models three weeks apart, and they point in opposite directions. Muse Spark 1.3, released September 2 2026, is the closed flagship: 1M context, sharper agentic coding, API-only. Muse Glimmer, released August 10 2026, is the open one: 30B dense parameters under Apache 2.0, distilled from Spark 1.2, built to run on a single consumer GPU.
In this guide I put both on the same spec sheet, explain what really changed since the Llama era, show you the verified Glimmer local quickstart, and close with an honest verdict on which one deserves your weekend.
1. The Spec Sheet: Two Models, Two Philosophies
Spark 1.3 is Meta Superintelligence Labs iterating on its proprietary line — Spark 1.0 in April 2026, then 1.1, then 1.2 on August 5 with the Muse Code terminal agent, the Meta Model API and OpenRouter. Glimmer is the same lab going the other way: open weights on Hugging Face from day one.
Muse Spark 1.3
Meta Superintelligence Labs · Closed · Sep 2 2026
- • 1M-token context window with native multimodal input
- • API-only as muse-spark-1.3, via Muse Code and the Meta Model API
- • Trained for agentic coding: Meta reports ~20% fewer tool calls and ~25% fewer tokens vs 1.2
- • Standard tier $1.25 input / $4.25 output per 1M tokens; contributor tier $0.10 / $0.20
- • Zuckerberg promised open Spark weights will follow
Muse Glimmer 30B
Meta Superintelligence Labs · Apache 2.0 · Aug 10 2026
- • 30B dense parameters + 1.8B vision encoder, distilled from Spark 1.2
- • 131K context, 100+ languages, multimodal chat
- • Runs on one consumer GPU: 4-bit quant fits under 20GB
- • Meta-reported: SWE-bench Verified 76%, GPQA Diamond 83.5%, OSWorld-Verified 65.9%
- • Runtimes: Ollama, LM Studio, llama.cpp, MLX, vLLM
Why this double release matters
Meta is splitting its strategy in two: a closed frontier line monetized through the API, and an open agentic line that wins developers’ machines. You no longer choose between Meta power and local control — you pick the right Muse for each job.
2. What Changed Since the Llama Era
Glimmer is Meta’s first open-weight release since Llama 4, and the license alone tells the story: Apache 2.0 replaces the Llama Community License, so commercial use, modification and redistribution work without the old gates.
The design target changed too. Llama competed on raw capability against GPT and Gemini. Glimmer competes on where it runs — always-on local agents, function calling, LLM-as-a-judge — distilled from the flagship instead of trying to be the flagship.
License:
Apache 2.0 — true open weights on Hugging Face as meta-models/Muse-Glimmer-30B.
Hardware:
One consumer GPU or Mac instead of a cluster. The 4-bit build fits under 20GB.
Lineage:
Distilled from Muse Spark 1.2, the closed flagship — not a separate Llama-style family.
Skills:
Tuned for tool calls with exact schemas, long-horizon plans, and recovery when tools fail.
The honest continuity
Llama made Meta the default for open weights, but rival labs set the pace through 2025 into 2026. Glimmer does not try to out-gun the biggest open models on raw scores — it stakes out the consumer-hardware agent lane where Meta can credibly lead.
3. Quickstart: Run Glimmer Locally in 5 Minutes
Every command below is verified against the official Ollama library page and the Hugging Face repo. No flags invented, no steps skipped.
Step 1 — Pull and run with Ollama
One command downloads and starts the model. On Apple Silicon with the MLX engine, use the muse-glimmer:30b-mlx tag instead.
ollama run muse-glimmer
ollama run muse-glimmer:30b-mlx
Step 2 — Talk to it over HTTP
Ollama serves a local API on port 11434. This exact call comes from the official library page:
curl http://localhost:11434/api/chat -d '{
"model": "muse-glimmer",
"messages": [{"role": "user", "content": "Hello!"}]
}'Step 3 — Same model from Python
Prefer code over curl? The official Ollama Python snippet works unchanged:
from ollama import chat
response = chat(
model="muse-glimmer",
messages=[{"role": "user", "content": "Hello!"}],
)
print(response.message.content)Prefer raw weights?
Grab meta-models/Muse-Glimmer-30B on Hugging Face and load it with llama.cpp, LM Studio, MLX or vLLM. The GGUF quant is the fastest path on a single GPU.
4. Honest Limits
Two strong releases, but neither is magic. Here is where each one bites.
- • Glimmer is 30B: it wins the single-GPU lane, not the frontier. For maximum reasoning depth you still call Spark 1.3 or a larger open model.
- • Every Glimmer benchmark in this guide is Meta-reported. Independent testing scores it below rivals like Qwen3.6-27B on several coding and knowledge tests.
- • 131K context is generous for local work, but it is not Spark’s 1M. Plan long-agent memory accordingly.
- • Spark 1.3 is API-only and proprietary. The cheap contributor tier lets Meta train on your usage — route anything sensitive through the standard tier.
- • Always-on local agents still hallucinate. Keep Glimmer on tool-mediated actions, not unsupervised factual claims.
The most common mistake
Treating Glimmer as a drop-in GPT replacement. It is a distilled agent specialist: schemas, tools, recovery. Ask it to be a general oracle and you will blame the model for a job it was never built to do.
5. Verdict
If you build agents that must run anywhere — offline laptop, on-prem box, privacy-sensitive client — Glimmer is the most interesting Meta release since the original Llama. Apache 2.0, one GPU, genuinely good tool use.
If you sell coding output by the token, Spark 1.3 is the workhorse: 1M context, fewer wasted calls, and a contributor tier priced for experimentation. Watch for the promised open Spark weights — that release would merge both lanes.
My verdict
Run Glimmer locally this weekend with the three commands above; point production coding at Spark 1.3 through Muse Code. That split — open agent on your machine, closed flagship in the cloud — is exactly the architecture Meta is betting on.
Sources
- Meta Research — Introducing Muse Spark 1.3 (Sep 2, 2026)
- Meta Research — Introducing Muse Glimmer (Aug 10, 2026)
- Ollama library — muse-glimmer (verified run command)
- Hugging Face — meta-models/Muse-Glimmer-30B
- Hugging Face blog — Muse Glimmer local and agentic setups
- Meta Developer Center — Muse Spark models and pricing
Conclusion
Meta closed August and opened September with a clear message: the flagship stays in the cloud, the agent moves onto your desk. Spark 1.3 pushes coding efficiency forward; Glimmer hands you 30B of distilled agency under Apache 2.0.
My recommendation stands: Glimmer on your machine for always-on agents, Spark 1.3 in Muse Code for heavy coding. When the open Spark weights land, I will update this guide — that is the release that could change both answers.
Double Release: Cheat Sheet
Run tonight
- • ollama run muse-glimmer
- • Curl the local API
- • Try :30b-mlx on Mac
Remember
- • Spark 1.3: closed, 1M context
- • Glimmer: Apache 2.0, 131K
- • Benchmarks are Meta-reported
Watch next
- • Open Spark weights
- • Community fine-tunes
- • Independent Glimmer evals



