A laptop computer running AI agent workflows locally, with glowing neural network visualisation on screen, no cloud connection needed
News

Meta's Muse Glimmer Runs a 30B Agent on Your Laptop — No Cloud Required

A 30-billion-parameter agent model distilled from Muse Spark, compressed to 17GB, running at 233 tokens per second on an RTX 5090 — entirely offline. Meta just made local AI agents practical.

Meta AIMuse GlimmerOpen Source AILocal AIAgentic AI

Meta just put a 30-billion-parameter AI agent model on your laptop. No cloud. No API key. No per-token bill. Muse Glimmer, released August 10 under Apache 2.0, is built for always-on local agent workflows — the kind that manage your schedule, read your screen, call tools, and recover from errors without phoning home.

The model is distilled from Muse Spark, Meta’s larger superintelligence-focused system. It ships with multimodal input (text and images), 131K context length, and a speculative decoding system that pushes throughput to 233 tokens per second on an RTX 5090. On Apple silicon, an M5 Max hits 50 tokens per second. That’s fast enough for real-time agent interaction, not just batch processing.

🔍 THE BOTTOM LINE

The practical takeaway: a capable agent model that runs entirely offline on consumer hardware, licensed for commercial use, beating Google’s Gemma4-31B and Qwen3.6-27B on agentic benchmarks. For organisations that need AI capabilities but can’t send data to a cloud — healthcare, legal, defence, financial services — this changes the calculus. It also aligns with a thesis we’ve been tracking: distributed AI running lean may matter more than frontier-scale cloud models for most real-world use cases.

Fitting 30B Into 24GB

The engineering story is where this gets interesting. A 30B model at full precision needs 55GB of memory — more than any consumer GPU provides. Meta compresses it to roughly 4-bit precision, bringing the language model under 20GB. Two quantised builds ship: K-Quant-Dynamic targets 32GB VRAM with 0.2% average accuracy degradation, and K-Quant-17GB targets 24GB VRAM at 1.0% degradation across 15 benchmarks.

The speed trick is DFlash, a block-diffusion drafter that predicts 16 tokens in a single forward pass. The main model verifies the block in parallel — accepting correct tokens, correcting wrong ones. This gives a 3.1x speedup on NVIDIA’s RTX 5090, 1.8x on Apple M5 Max, and 1.5x on M4 Max. The output is identical to standard generation; only the delivery is faster.

What It Actually Does Well

Meta evaluated Muse Glimmer against Gemma4-31B and Qwen3.6-27B across agentic, coding, multimodal, safety, and reasoning benchmarks. The results, detailed by Marktechpost, show a clear pattern:

  • Agentic orchestration: Muse Glimmer leads on MCP Atlas (75.5 vs 54.2 and 62.5), DeepSearch QA (74.6), and SWE-Bench Pro (51.2)
  • Reasoning: AIME 2026 at 94.7, IFBench at 77.0
  • Where it trails: Qwen3.6-27B stays ahead on OSWorld-Verified (75.6 vs 65.9) and TerminalBench 2.1 (60.7 vs Muse Glimmer’s score)

The model handles function calling with precise schemas across extended workflows, chains reasoning over long horizons, and — critically for agent reliability — diagnoses and retries failed tool calls rather than halting. It accepts interleaved text and images through a dedicated perception encoder, enabling screenshot interpretation and document analysis.

Meta states the model does not meet their Frontier AI definition under the Advanced AI Scaling Framework, rating chemistry/biology, cyber, and loss-of-control risk at moderate or lower.

Why Local Agents Matter Now

The case for local AI isn’t new, but the capability gap between cloud and local has been closing steadily. What makes Muse Glimmer different is the combination of three things that haven’t coexisted in a single model before: frontier-adjacent agentic capability, practical speed on consumer hardware, and a permissive licence.

For New Zealand, this matters in a specific way. Data sovereignty is a live concern — government agencies and healthcare providers face restrictions on sending data offshore to US-based AI services. A model that runs locally, on hardware already sitting on desks, sidesteps that problem entirely. The AI boom pushing up electronics prices is one side of the coin; models that reduce the need for expensive cloud subscriptions are the other.

The model is available now on Hugging Face, with integrations coming for Ollama, LM Studio, llama.cpp, MLX, and ExecuTorch. AMD, Arm, Dell, Intel, and NVIDIA are all working on optimised deployments.

The Catch

Three things worth noting. First, “30B parameters” and “runs on a consumer GPU” sounds great until you realise the 24GB VRAM requirement means an RTX 3090 or better — hardly ubiquitous hardware. Mac users need an M4 Max or M5 Max with unified memory. This is “consumer” in the enthusiast sense, not the Chromebook sense.

Second, the benchmark lead on agentic tasks is real but narrow. Qwen3.6-27B outperforms on computer-use and terminal benchmarks — the tasks that involve actually navigating an operating system. If your agent needs to click through a GUI, Muse Glimmer may not be the best pick.

Third, open weights under Apache 2.0 means no built-in safety guardrails. Meta’s documentation advises adding system-level guardrails rather than deploying the model as a bare endpoint. That’s responsible guidance, but it shifts the safety burden onto every individual deployer — and not everyone will bother.

❓ FAQ

Can I run Muse Glimmer on my current computer? If you have a GPU with 24GB VRAM (RTX 3090, 4090, 5090) or an Apple Mac with M4 Max / M5 Max and 32GB+ unified memory, yes. The K-Quant-17GB build is the one to try first. Anything less powerful won’t fit the model in memory.

How does it compare to running Claude or GPT-5 locally? It doesn’t, directly — those models are cloud-only at much larger scales. Muse Glimmer’s competitors are other open-weight models in the 27-31B range: Google’s Gemma4-31B and Alibaba’s Qwen3.6-27B. Muse Glimmer leads on agentic benchmarks but trails on computer-use tasks.

What does “agentic” actually mean here? The model is trained to do multi-step workflows: call tools, read results, decide what to do next, recover from errors, and sustain a plan across many turns. A chatbot answers one question. An agent manages a process.

Is this relevant to New Zealand? For organisations with data sovereignty requirements — government, healthcare, iwi organisations managing sensitive data — a capable local model removes the dependency on US cloud providers. It also reduces ongoing API costs, which are typically billed in USD.

📰 Sources

— CJ Murden, editor of Singularity.Kiwi. Former digital technologies teacher, author of AI-focused books. Writing with a New Zealand focus.

Sources: Meta AI Research Blog, Marktechpost, Hugging Face