Muse Spark Open: Meta’s 816B Open-Weight Multimodal Agent Model
Meta released an 816B-parameter open-weight multimodal model that activates roughly 42B parameters per token and targets long-horizon agentic coding with a 1M-token context window.
Key takeaway
Muse Spark Open combines sparse MoE routing with text, image, video and audio perception. It is available in BF16 and NVFP4 checkpoints and is supported by several inference stacks, but the full weights still impose substantial hardware requirements.
Updated on Oct 20, 2026
01
Abstract
What launched this week?
Meta released Muse Spark Open on 15 October 2026. It is the open-weight release of the Muse Spark model family, built for coding agents and long-horizon work. The headline is the combination of sparse compute, native multimodal input, and a very long context window—not a claim that all 816B parameters run for every token.
02
Introduction
Architecture: large model, sparse token compute
The language backbone is a 62-layer mixture-of-experts Transformer. Each token is routed to 8 of 256 experts in each MoE layer, so only a fraction of expert parameters is active for a token. Sparse activation reduces per-token computation, but it does not eliminate the need to store or distribute the full checkpoint during inference.
03
Problem
Multimodal perception and long context
Muse Spark Open accepts text, images, audio and video and produces text. A shared perception encoder handles images and video frames, while a separate compact audio encoder turns waveform segments into audio tokens. The model can therefore reason over mixed evidence such as code, screenshots, video frames and audio, which is useful for debugging workflows that cannot be described as text alone.
04
Background
Why it targets agentic coding
The model is designed for multi-step workflows: inspect a codebase, plan a change, invoke tools, observe failures, and revise the result. This differs from optimizing only for a single code completion. Meta describes internal demonstrations that used Muse Code to modify and build an open-source iOS app and to edit video in DaVinci Resolve. These are vendor demonstrations, not independent benchmark results.
05
Methodology
Inference formats and deployment requirements
Muse Spark Open — official article thumbnail
Original thumbnail associated with the Hugging Face technical article about Meta Muse Spark Open. Used as the article image; not AI-generated.
Hugging Face blog repository, meta-muse-spark-open.md frontmatter
06
Architecture
Serving optimizations and speculative decoding
Inference partners report optimizations for the model’s sparse routing and long context. vLLM documents DSpark speculative decoding, which proposes several draft tokens using block diffusion and verifies them with the main model. These speed claims depend on hardware, batch size, context length, acceptance rate and software version; do not treat them as universal latency guarantees.
07
Dataset
Benchmarks: what can be claimed today?
Meta’s launch page points readers to an evaluation methodology report and detailed model card rather than supplying a complete, independently reproducible benchmark table in the announcement itself. This article therefore focuses on disclosed architecture, deployment and implementation details. Performance statements from Meta, NVIDIA and vLLM are attributed to those sources and should not be interpreted as neutral cross-model rankings.
08
Training
Safety, license and limitations
The open-weight release includes additional safety post-training, and Meta says it assessed the model under its own scaling framework. That is not a substitute for application-specific safeguards. The Muse Model License allows broad use subject to its stated conditions and is not interchangeable with Apache 2.0. Teams should review the actual license and model card before deployment.
09
Experiments
Primary sources and engineering takeaway
Muse Spark Open is notable because it combines open weights, sparse 816B-scale MoE architecture, native multimodal input and a 1M context window with day-one support across multiple inference stacks. Its practical cost is determined not just by the active parameter count but by checkpoint precision, resident memory, inter-GPU communication, KV cache, speculative decoding and the agent harness around it.
Result board
Official Meta release
https://research.meta.ai/blog/muse-spark-open
Model card and weights
https://huggingface.co/meta-models/Muse-Spark-Open-816B-A42B
Hugging Face technical walkthrough
https://huggingface.co/blog/meta-muse-spark-open
vLLM architecture and inference details
https://vllm.ai/blog/2026-10-15-muse-spark-open
NVIDIA deployment and throughput report
https://developer.nvidia.com/blog/scale-agentic-coding-workflows-with-metas-muse-spark-open-on-nvidia-gb300-nvl72/
Meta deployment requirements
https://dev.meta.ai/docs/muse-spark-open
10
References
Source trail
Primary papers, implementation pages, and external source records used to ground this explainer.
Continue reading
Related research
LFM2.5-24B-A2B
LFM2.5-24B-A2B is a 24B-parameter hybrid MoE reasoning model with low active compute, a 131K context window, and training optimized for local tool-using agents.
AI ModelsOpus 5.5 — What Changed
Opus 5.5 is less about a new visible model architecture and more about making frontier-style work cheaper, more efficient, and easier to sustain.