Meta releases Muse Glimmer: 30B Apache-licensed open-weight AI model for local agent workloads

On August 10, 2026, Meta Superintelligence Labs released Muse Glimmer, a 30-billion-parameter model built for always-on local agent workflows, and open-sourced the weights under the permissive Apache 2.0 license. The pitch is direct: it runs on a Mac or PC with a single consumer GPU, works with or without an internet connection, and targets the workloads that actually matter for agents: function calling, local coding, long tool-use sessions, and LLM-as-a-judge evaluation. The weights are on Hugging Face today, with developer documentation and optimized integrations for llama.cpp, MLX, and ExecuTorch landing in the coming days. If you have been building agents that call tools, this is the release worth reading closely. I build AI agents with Spring AI for a living, and the agentic framing here is what sets it apart from another chat model drop. This article breaks down what Muse Glimmer is, how Meta trained it, how it fits on a laptop, and what it changes for developers who ship agentic features. Why Local Agents Are the Point Almost every agent you can run today lives on someone's server. The model, the context, the tool calls, and the conversation history round-trip through a cloud API. That works until the network drops, until the data is sensitive, or until the per-token bill for a long agent session makes you think twice. Local inference removes those three constraints at once. An agent that manages your schedule, drafts your messages, and organizes your files is handling personal context that most users would rather not send anywhere. And the open source community has already shown the pattern: smaller models, trained effectively, can approach frontier-level performance on targeted tasks. Muse Glimmer is Meta's bet that the same logic holds for agentic work, not just chat. How Meta Trained It An agent that runs continuously needs several capabilities working together: long-horizon execution, precise tool calling, multimodal understanding, long-context memory, and instruction following. Training a 30B model for that balance took three phases: Pre-training. The model was trained on Muse Spark's outputs using logit distillation, with a similar data mix to the teacher model. This phase produces the compact base. Mid-training. Longer-context, agent-heavy data with richer reasoning traces, alongside organic data. This phase pushes the model toward sustained multi-step work. Post-training. Supervised fine-tuning combined with on-policy distillation and reinforcement learning across general, reasoning, coding, and agentic domains. Meta also evaluated the model under the standards in its Advanced AI Scaling Framework and assessed it for open-weight release across every relevant category before publishing the weights. What It Can Do Muse Glimmer is trained and evaluated for the specific behaviors that make an agent useful: End-to-end agentic task completion. Strong success rates on full-task benchmarks including DeepSearch QA, MCP-Atlas, tau-Bench, and SWE-Bench, which test working within scaffolds, writing and debugging code, and resolving multi-turn requests from start to finish. Reliable tool use. It handles a wide range of function calls and invokes tools with precise schemas through extended workflows. Multi-step reasoning. It chains reasoning over long horizons and sustains coherent plans across complex workflows. Failure recovery. When a tool call fails or returns an unexpected result, it is trained to diagnose the error and retry rather than halt. This is the behavior that separates a usable agent from a demo. Multimodal input. A dedicated perception encoder accepts interleaved text and images, so agents can interpret screenshots, charts, and documents alongside conversation. Scaffold compatibility. It works across OpenClaw and other agentic orchestration patterns, so it can drop into existing setups. Controllable effort. Different reasoning strengths let you choose the balance between quality and speed per task. Multilingual. Trained on data from more than 100 languages. How It Performs Meta compared Muse Glimmer against Gemma4-31B and Qwen3.6-27B across agentic, coding, multimodal, safety, and reasoning benchmarks, and the claim is measured: the model performs strongly for its size class. The benchmark tables in the announcement show how it stacks up against its direct competitors, and the full methodology report covers how the evaluations were run. The framing matters. This is not a claim that a 30B model beats frontier-scale models. The point is that for the agentic workloads people actually run locally, this size class is now competitive, and you can own the weights. How a 30B Model Fits on a Consumer GPU At full precision, a 30-billion-parameter model needs over 55 GB of memory, far beyond any consumer GPU. Meta applied two optimizations to close that gap. First, quantization. The weights are compressed to approximately 4-bit precision, shrinking the language model to under 20 GB. That leaves headroom for the KV cache, the perception encoder for image understanding, and the speculative decoding drafter to run together inside a 24 GB or 32 GB envelope. Meta ships K-Quant-Dynamic and K-Quant-17GB variants and says the compression introduces minimal to no degradation on agentic tasks, which is the claim that matters for production use. Second, faster generation. Language models normally generate one token at a time, which feels slow during long reasoning chains or multi-step tool calls. Muse Glimmer ships with a lightweight drafter based on DFlash, a small companion network that proposes entire blocks of tokens at once. The main model verifies the proposals in parallel, accepting correct tokens and correcting wrong ones. The output quality is identical to standard generation, and the speed difference is the whole point of the design. Measured on the K-Quant-17GB model with the quantized DFlash drafter, decode speed improves by 3.1 times on an RTX 5090, 1.8 times on an M5 Max, and 1.5 times on an M4 Max. That is the difference between a model that feels like a server round-trip and one that feels like a local conversation. An agent that takes minutes to plan its next step breaks the flow of real work; one that responds in seconds does not. What an Always-On Agent Looks Like Meta positions Muse Glimmer for the use cases where an agent earns its keep by staying resident on the device: managing your schedule, drafting your messages, organizing your files, and learning how you work over time. These are not one-shot Q&A tasks. They are persistent loops where the agent watches context, decides when to act, calls a tool, checks the result, and keeps going. That is exactly the workload where cloud round-trips hurt most, because the latency penalty is paid on every step of a long chain, not once per prompt. The design choices follow from that target. The perception encoder exists because agents need to read screenshots and documents, not just text. The failure-recovery training exists because a long-running agent will hit a tool that returns garbage, and the difference between a useful agent and a stuck one is what happens next. The controllable effort setting exists because a calendar check should be fast and a code review can afford to think longer. Every capability in the release traces back to the always-on requirement. Local vs Hosted Agents: What Actually Changes If you are already running agents against a hosted API, the honest question is what moving local gives you. The trade-offs are concrete: Cost model. Hosted agents bill per token, and agentic loops multiply token usage: every tool call, retry, and failed attempt is a request. A local model turns that variable cost into a fixed hardware cost. The model does not charge you for trying again. Latency. A local model skips the network round-trip, and with speculative decoding the perceived speed improves further. For interactive agents this is the difference between a tool that feels responsive and one that feels like a ticket system. Privacy. Personal context stays on the device. For a schedule manager or a document organizer, that removes the single biggest objection users have to agentic features. Capability ceiling. A 30B model is not a frontier model. For open-ended reasoning on hard problems, a hosted frontier API will still win. The local model covers the high-frequency, well-scoped agent tasks, and that is a large share of real agent traffic. Operations. You own the maintenance. No API keys, no rate limits, no vendor deprecation, but also no one else watching the model for you. A 30B model on a 24 GB machine is a real resource footprint, so the machine needs to be dedicated to it. The pattern that makes sense to me is hybrid: run the repetitive, sensitive, high-frequency agent work locally, and escalate the hard reasoning to a hosted frontier model when the local one is out of its depth. Apache 2.0 makes that easy, because there is no licensing friction in putting the local model inside a commercial product. The Ecosystem Around It Meta is not asking you to build your own toolchain. The integrations map to what developers already use: Run it locally: Ollama, LM Studio, and Unsloth support it. Edge frameworks: llama.cpp, ExecuTorch, and MLX are the deployment paths. Scale-out serving: vLLM and SGLang cover server-side deployment. Hosted APIs: Together AI, Fireworks AI, and OpenRouter offer managed access. Fine-tuning: PyTorch's TorchTitan training features let you tune the model for your own use case. Meta is also working with AMD, Arm, Dell, Intel, and NVIDIA to optimize performance across devices, and the AI Developer Center page includes guidance on custom scaffolds so you can plug your own orchestration in on day one. What This Means for Developers For anyone building agents in production, this release changes a calculation that has been fixed for the last two years. Right now, agent economics work like this: every tool call, every retry, every failed attempt is tokens on someone else's infrastructure, billed per request. A local agent inverts that. The cost becomes hardware you already own, the data never leaves the device, and the agent keeps working in a tunnel, on a plane, or on a client site with no network. The Apache 2.0 license matters just as much as the hardware story. Open weights under a permissive license means you can ship a commercial product on top of this model without royalty obligations, which is not something you get from every frontier lab. The remaining unknown is operational: a 30B model on consumer hardware is still a real resource footprint, and the agentic benchmark scores need to hold up in your specific scaffold, with your specific tools. My take is that the combination is what makes this release different. A capable, permissively licensed, agentic model that runs on a laptop, with the tool ecosystem already lined up, gives the local-agent idea its first realistic default choice. The weights are live on Hugging Face, and the developer docs walk through running your first agent. If you were going to move one agent workload off the cloud tomorrow, which one would it be? I would start with the LLM-as-a-judge pipeline, since it is cheap to run, repetitive, and painful to pay per token for. Let me know what you would pick.

Meta today released Muse Glimmer, a 30-billion-parameter open-weight model designed to run autonomous AI agents directly on consumer hardware — pushing agentic workloads that normally depend on cloud infrastructure onto high-end Macs and PCs.Just as notable as what the model does is how it's licensed. Glimmer arrives under the permissive, industry-standard Apache 2.0 open source license — the company's first fully open release since it succeeded its open-weight Llama family in April with the proprietary Muse Spark.In fact, Muse Glimmer launches today with a more permissive license than Llama ever carried. Llama's bespoke community license drew years of criticism for restrictions like its 700-million-monthly-user cutoff; Apache 2.0 has no such strings, permitting unrestricted commercial use, modification and redistribution.The weights are available on Hugging Face now. Wang said support is rolling out this week through Ollama, LM Studio, vLLM, SGLang, Together AI, Fireworks AI and OpenRouter, with optimized llama.cpp, MLX and ExecuTorch integrations landing in the coming days; Meta's blog post also names Unsloth as a local-runtime partner and points to PyTorch's TorchTitan for fine-tuning. The company says it is working with AMD, Arm, Dell, Intel and Nvidia to optimize performance across devices, and has published developer documentation covering custom agent scaffolds."Today we're also opening the weights for Muse Glimmer, a great 30B parameter dense model that can run locally," Meta co-founder and CEO Mark Zuckerberg wrote in a post on X (under his longtime handle @finkd). "Soon we'll also release the weights for Muse Spark 1.2, our latest foundation model. Meta is a strong supporter of open source and I'm proud of these releases."That promised Muse Spark 1.2 release would be an even bigger shift: it's the frontier model behind Muse Code, the terminal coding agent Meta shipped just five days ago, and until today the entire Muse family was proprietary. Zuckerberg had teased at that launch that he'd "have more to share soon" on open source. Now we know what he meant.For developers and enterprises, the practical stakes of local inference go beyond where computation happens. An agent working with files, screenshots, development environments and other sensitive context can execute those workflows without continuously sending that information to a remote inference service. Local deployment also removes network availability and per-token API charges from the inference loop — although organizations still bear hardware, electricity, deployment and management costs.A 30B model built around the agent loopRather than positioning Glimmer primarily as a general chatbot, Meta trained it around the sequence of operations an autonomous agent performs: formulate a plan, call tools, interpret the results, continue working, and recover when something goes wrong."Just like much larger models, muse glimmer can operate as a fully capable agent via planning, tool calls, checking its own results, and failure recovery," Alexandr Wang, Meta's chief AI officer, wrote in a thread on X announcing the release, adding that the model "can run on 24GB of VRAM without losing agentic reliability."According to the model card on Hugging Face, Glimmer is a dense causal transformer with approximately 29.6 billion total parameters across 52 layers, including a dedicated ~1.8B-parameter ViT-G/14 perception encoder. It accepts interleaved text and images, produces text, supports more than 100 languages and has a stated context length of 131,072 tokens or more, with a knowledge cutoff of January 4, 2026.That combination is intended to let an agent interpret screenshots, charts and documents while simultaneously reasoning about text and invoking external tools. Glimmer offers low, medium, high and xhigh reasoning settings — set via the system prompt — so applications can dial reasoning effort up or down per task, and Meta says it works across agentic scaffolds including OpenClaw and Hermes Agent.The model is a distillation of Meta's larger flagship: per the company's technical blog post, Glimmer was pre-trained on Muse Spark's outputs using logit distillation, mid-trained on longer-context, agent-heavy data with richer reasoning traces, then post-trained with supervised fine-tuning, on-policy distillation and reinforcement learning across general, reasoning, coding and agentic domains.Meta demonstrated the result with a local Home Assistant workflow: in a demo video, Glimmer autonomously discovers a Home Assistant instance on the network via tool calls, queries device APIs, writes a responsive HTML/CSS/JavaScript dashboard from scratch and deploys a local server to verify its own work. That's closer to the operational reality of enterprise agent deployments than a standalone question-answering benchmark — the model has to maintain a plan while interacting with external systems, then inspect whether its actions produced the expected result.Compressing an agent into 24GBThe hardware story is central to the release.At full precision, Meta says the 30B model requires more than 55GB of memory — beyond any single consumer GPU. The company therefore developed approximately 4-bit quantized versions that shrink the language-model weights to under 20GB, leaving headroom for the pieces an operational agent also needs in memory: the KV cache, the perception encoder and a companion speculative-decoding model, all fitting within a 24GB or 32GB envelope.In practical terms, that means the quantized builds run on consumer machines — though the upper end of them. The 24GB-targeted K-Quant-17GB configuration fits on a single high-end consumer graphics card, such as Nvidia's RTX 3090 or RTX 4090 (both with 24GB of VRAM), while the 32GB-targeted K-Quant-Dynamic version lines up with the newer RTX 5090's 32GB. On the Mac side, Apple Silicon's unified memory plays the role of VRAM, so a MacBook Pro or Mac Studio with 32GB or more of memory can hold the full stack — Meta ran its own speed tests on M4 Max and M5 Max MacBook Pros. A typical 8GB or 16GB laptop, however, remains out of reach, and the full-precision BF16 release — which Meta pegs at 64GB — stays in the territory of data-center GPUs and top-spec Mac Studio configurations.Meta reports average accuracy degradation of just 0.2% across 15 benchmarks for its K-Quant-Dynamic version targeting 32GB hardware, and 1% for the K-Quant-17GB configuration targeting 24GB hardware. Those figures are Meta's own measurements, not independent evaluations.Meta is also using DFlash speculative decoding to attack the other big problem with local agents: latency. Instead of generating every token sequentially, a smaller DFlash "drafter" model proposes blocks of 16 tokens that the primary model verifies in parallel, producing identical output faster.Meta reports this raises average generation speed on an Nvidia RTX 5090 from 74.9 tokens per second to 233.4 — a 3.1x increase. An Apple M5 Max rises from 26.6 to 50.2 tokens per second (1.8x), and an M4 Max from 23.7 to 37.8 (1.5x). The tests used batch size one and greedy decoding, with Apple systems measured via ExecuTorch and the RTX 5090 via llama.cpp.For agent applications, those multipliers matter more than they would for chat: a single user request can trigger many model turns, tool calls and verification steps, and latency accumulated at every stage can quickly make an otherwise capable agent impractical.Glimmer enters an increasingly competitive local-model marketMeta is not entering an empty field. Developers already have capable open-weight models in this size class, most prominently Google's Gemma 4 family and Alibaba's Qwen3.6-27B — both of which position themselves around reasoning, multimodal understanding and agentic workloads. Meta's own benchmark table compares directly against both.Glimmer leads that three-way comparison on several agentic tests, including MCP Atlas at 75.5, DeepSearch QA at 74.6, τ³-Banking at 23.5, WildClawBench at 47.6 and GAIA2 at 43.3. It scores 51.2 on SWE-Bench Pro, versus 36.9 for Gemma4-31B and 50.2 for Qwen3.6-27B in Meta's evaluation.But Glimmer does not sweep the field. Qwen leads Meta's own comparison on OSWorld-Verified (75.6 vs. Glimmer's 65.9), TerminalBench 2.1 (60.7 vs. 51.7), SkillsBench, GDPval-AA (1141 vs. 953) and most of the multimodal benchmarks. On SWE-Bench Verified, Glimmer's 76.0 lands just below Qwen's 77.2. Gemma leads on GPQA Diamond and Humanity's Last Exam.Read honestly, the numbers make Glimmer more interesting as a specialized local-agent model than as evidence of a universal performance lead. For enterprise developers, the practical question is whether its combination of agent reliability, quantization quality, tool compatibility and decoding speed translates from benchmarks into sustained real-world workflows.ModelDeveloper / originAA scoreParameters / contextLowest tracked API priceAccessLicenseStrongest use casesKimi K3Moonshot AI; China602.8T total / 104B active; 1M$3.00 input / $15.00 output via Kimi, Fireworks or Modal (pricing)WeightsKimi APICustom Kimi K3 license. Large model-as-a-service operators above $20M in 12-month revenue need a separate agreementLarge products may need to display “Kimi K3.”Frontier long-horizon codingMultimodal research and complex tool-driven agentsGLM-5.2Z.ai / Zhipu AI; China53753B / 40B active; 1M$0.75 / $2.40 via DeepInfra FP4 (pricing)WeightsZ.ai APIMITLong-horizon coding and agentsMillion-token analysis with adjustable reasoningDeepSeek V4 Flash 0731DeepSeek; China52284B / 13B active; 1M$0.09 / $0.18 via DeepInfra (pricing)WeightsDeepSeek APIMIT• Extremely economical reasoning• Coding agents, terminal work and tool useMiniMax-M3MiniMax; China45428B / 23B active; 1M$0.23 / $0.96 via CoreWeave (pricing)Weights; MiniMax APIMiniMax Community License. Commercial attribution required; companies above $20M yearly revenue need authorization. Includes prohibited-use conditions.• Native text, image and video work• Long-context coding and “cowork” agentsMiMo-V2.5-ProXiaomi; China431.02T / 42B active; 1M$0.35 / $0.70 via GMI (pricing)WeightsXiaomi APIMITComplex software engineeringAgents spanning thousands of tool callsInklingThinking Machines Lab; U.S.42975B / 41B active; 1M in weights$0.95 / $4.05 via DeepInfra FP8 (pricing)WeightsTinkerApache 2.0Customizable text, image and audio foundationFine-tuned coding, RAG and tool-use systemsNemotron 3 Ultra 550B A55BNVIDIA; U.S.38550B / 55B active; up to 1M in weights$0.37 / $1.08 via Blackbox AI (pricing)WeightsOpenMDW-1.1; permissive commercial and derivative-model rightsComplex agents and long-context reasoningHigh-accuracy RAG, code, math and scienceMistral Medium 3.5Mistral AI; France30128B dense; 256K$1.50 / $7.50 via Mistral (pricing)WeightsMistral APIModified MIT. Companies above $20M consolidated monthly revenue must obtain a commercial license or use Mistral’s service.Coding agents and function callingMultimodal instruction followingGemma 4 31BGoogle DeepMind; U.S.3030.7B dense; 256KFree on Google AI Studio’s limited tier; paid low $0.10 / $0.34 via CoreWeave (pricing)WeightsGoogle AI StudioApache 2.0Compact multimodal reasoning and codingManageable local or private-server deploymentsgpt-oss-120bOpenAI; U.S.24117B / 5.1B active; 131K$0.03 / $0.17 via CoreWeave (pricing)Weights Numerous third-party APIsApache 2.0Reasoning structured output and toolsFine-tuning and single-80GB-GPU deploymentCommand A+Cohere; Canada23218B / 25B active; 128K inputFree on Cohere’s currently tracked endpoint (pricing)WeightsCohereApache 2.0Enterprise RAG and grounded citations• Multilingual agents and document processingMuse Glimmer 30BMeta; U.S.Not yet scored29.6B dense, including vision encoder; 131K+No public metered hosted price located on launch dayWeightsMeta model pageApache 2.0 for full-precision weights, quantizations, drafter and perception encoderAlways-on local agents on 24–32GB systemsTool use, recovery, coding and screen/document understandingMeta Glimmer adds to a still-small roster of genuinely open, frontier-class models from U.S. companies.For the last two years, Chinese companies have set the pace in open source AI, with DeepSeek, Alibaba's Qwen team, Moonshot AI's Kimi, Zhipu's GLM and MiniMax shipping frontier-class open models under MIT and Apache 2.0 licenses on a cadence Western labs haven't matched. The usage data reflects it: by May 2026, Chinese open-weight models accounted for roughly 61% of all tokens consumed on OpenRouter, with four of the five most-used models coming from Chinese labs — while Meta's Llama, the prior open-weight leader, fell off the rankings entirely.The U.S. counterexamples remain countable on one hand: OpenAI's gpt-oss-120b and gpt-oss-20b, released under Apache 2.0 in August 2025 as the company's first open weights since GPT-2; Google's Gemma family, which is open-weight but ships under Google's own more restrictive custom license rather than an OSI-approved one; and Thinking Machines' Inkling. Glimmer invites the most direct comparison to gpt-oss: both are Apache 2.0, both offer adjustable reasoning effort, and both target self-hosted deployment. But the gpt-oss models are text-only, sparse mixture-of-experts designs built primarily for reasoning and tool use — gpt-oss-20b fits in about 16GB of memory while gpt-oss-120b targets a single 80GB data center GPU. Glimmer stakes out different ground: a dense model with native vision input, trained end-to-end around the agent loop, shipping with its own quantized variants and speculative-decoding drafter tuned for 24GB consumer machines. And if Zuckerberg follows through on opening Muse Spark 1.2's weights, Meta would put an actual U.S. flagship frontier model into open circulation — something no American lab has done at that tier.Safety remains part of the deployment architectureGiving a local model access to tools creates a different security problem from deploying a local chatbot — and Meta's own safety numbers show Glimmer is not uniformly stronger than its peers.On CI Memories, a privacy benchmark where lower violation rates are better, Glimmer records 26.4 against Gemma's 12.1 and Qwen's 53.4. On Siren AgentDojo, a prompt-injection test, Glimmer shows a 28.4% attack-success rate versus 25.6% for Gemma and 40.3% for Qwen — while posting the highest utility score of the three at 94.2.Meta says it evaluated Glimmer under its Advanced AI Scaling Framework and determined the model does not meet the framework's definition of "Frontier AI" because it is generally less capable than Muse Spark. Its Preparedness Team assessed Glimmer at Moderate or lower risk across chemical/biological, cyber and loss-of-control categories — the latter two inferred from the fact that Glimmer is broadly weaker than Muse Spark 1.0, which received the same designations.The company nevertheless recommends deploying Glimmer as part of a broader system with guardrails, including human-in-the-loop confirmation for irreversible actions. That caveat matters especially for local agents: keeping data on-device reduces exposure to cloud infrastructure, but local execution does not by itself solve prompt injection, excessive permissions or an agent taking an unintended action.Apache 2.0 weights and a fast-growing runtime ecosystemMeta is releasing full-precision BF16 weights, both 4-bit quantized variants, the DFlash drafter and the perception encoder — all under Apache 2.0. There is no Meta API price attached to the downloadable model, leaving total cost dependent on local hardware or whatever third-party hosting developers choose. One nuance worth noting for procurement teams: as with most "open source" model releases, it is the weights that are open — Meta has not released the training data or training code.The broader implication is that Meta is treating the developer workstation as a credible deployment target for autonomous agents, rather than merely a place to experiment with smaller language models. Glimmer's 30B size and 24GB target put that proposition within reach of high-end consumer hardware, while the Apache 2.0 license gives developers — and their legal departments — unusual freedom to modify and deploy it.The next test is whether its benchmark advantages survive the messier conditions of real software repositories, enterprise tools and long-running agent sessions. If they do, the most consequential part of Glimmer may not be another set of benchmark scores — it may be that a class of agent previously expected to live behind a cloud API can increasingly live, and work, on the machine sitting under a developer's desk.