Meta released Muse Spark on April 8, 2026. The model is the first from Meta Superintelligence Labs, the AI research unit Mark Zuckerberg created after he concluded that the Llama 4 family, released in April 2025, had failed to gain developer traction or close the performance gap against OpenAI and Anthropic. To staff the unit, Zuckerberg paid $14.3 billion for a 49 percent stake in Scale AI and brought Alexandr Wang, the data-labeling company’s co-founder and chief executive, to lead it. Wang’s team spent nine months rebuilding Meta’s AI stack from scratch. Muse Spark, internally codenamed Avocado, is the first output.
Three things separate it from any previous Meta model. It is the first Meta model that reasons step by step rather than producing an instant answer from training data alone. It is natively multimodal from the ground up, meaning vision and language share the same internal representation rather than being joined by an adapter layer after training. And it introduces a mode called Contemplating that scales inference compute by running multiple AI agents in parallel against the same problem. On the Artificial Analysis Intelligence Index, the independent benchmark Meta chose to anchor its launch claims, Muse Spark scored 52, placing it fourth, behind Gemini 3.1 Pro Preview and GPT-5.4 (both at 57) and Claude Opus 4.6 at 53.
This is a different release than Llama 4 was. Understanding what changed requires understanding what the company actually built.
The architecture Meta rebuilt
Meta’s technical blog describes the core design philosophy as deliberately staged: build a small model first, validate the architecture and training methodology, then scale. Muse Spark is intentionally small and fast by design. The headline claim is compute efficiency, and Meta’s framing is more precise than most benchmark announcements. The team fit a scaling law across a series of small experimental models, located the compute-to-capability frontier for their architecture, and found that Muse Spark reaches the same performance level as Llama 4 Maverick with more than 10x less training compute. The claim is not that Muse Spark exceeds Llama 4. It is that it matches it far more efficiently. If the scaling law holds at larger model sizes, and Meta is explicitly betting it does, this efficiency advantage compounds across the Muse family.
Three architectural decisions define what was rebuilt.
The first is multimodal integration. Every prior Meta model handled images through a pipeline: a vision encoder processes the image, projects its embeddings into the language model’s token space through an adapter, and the combined sequence passes through the language model. The join between the visual representation and the language representation, what researchers call the “stitching” approach, introduces distortions in tasks requiring tight integration of spatial and linguistic reasoning, such as reading circuit diagrams, interpreting scientific figures, or following step-by-step illustrated instructions. Muse Spark was trained from initialization with a unified representation across modalities. Visual tokens and language tokens occupy the same latent space and attend to each other with the same mechanisms throughout the model’s depth. Meta calls this visual chain of thought: the model can annotate a visual scene, track the spatial positions of objects across a multi-step reasoning process, or compare two images mid-inference. For structured visual-STEM problems, Meta reports notable improvements over the stitched architecture.
The second decision is the reasoning mode. Llama 4 and all prior Meta models used autoregressive generation, producing outputs as a function of the input sequence in a single forward pass. Muse Spark allocates computation to a reasoning phase before generating a final output. During this phase, the model decomposes the problem, generates and evaluates intermediate steps, and applies verification before committing to an answer. The specific training signals that shaped this behavior, whether reinforcement learning from human feedback, process reward models, or outcome-based reinforcement, are not detailed in the published material. The result is that Muse Spark can show its work in a way that no prior Meta model could.
The third decision is the Contemplating mode. To scale inference compute without proportionally increasing latency, Meta chose horizontal parallelism over sequential chain lengthening. In Contemplating mode, Muse Spark spawns multiple subagents that tackle the same problem from different approaches simultaneously. Wang described the design principle on Threads: “To spend more test-time reasoning without drastically increasing latency, we can scale the number of parallel agents that collaborate to solve hard problems.” Each subagent returns a partial solution. The system synthesizes a final answer from the ensemble. Meta does not publish the synthesis mechanism, specifically how conflicts between subagent outputs are resolved or how the system weights their contributions. In Humanity’s Last Exam, Contemplating mode achieved 58 percent. In the FrontierScience Research benchmark, it reached 38 percent.
The benchmark position and what to believe
Fourth place on the Artificial Analysis Intelligence Index is a real position, not a framing choice. Gemini 3.1 Pro Preview and GPT-5.4 both score 57. Claude Opus 4.6 scores 53. Muse Spark scores 52. These gaps are within the uncertainty bounds of most benchmark evaluations, but they are not manufactured by a hostile interpretation of the data. The model is competitive without being leading.
Where Muse Spark does lead, and the figure Meta emphasizes most, is token efficiency during evaluation. To complete the full Artificial Analysis Intelligence Index, Muse Spark used 58 million output tokens. Claude Opus 4.6 used 157 million. GPT-5.4 used 120 million. For the same benchmark performance tier, Muse Spark’s reasoning is more compressed. For organizations running large-scale inference, output token count directly determines cost, so this efficiency gap is the relevant commercial argument, not raw score.
Context matters for evaluating the benchmark claims. In April 2025, Meta submitted Llama 4 Scout to the Chatbot Arena benchmark using a fine-tuned model specifically optimized for that evaluation, not the variant available for download. When independent researchers reproduced the results with the publicly available weights, the performance gap was substantial. Meta acknowledged the discrepancy afterward. Muse Spark’s launch provides no additional transparency on whether the evaluated model matches the model API partners actually receive. Meta states that independent validation will follow the launch but specifies neither timing nor who conducts it. The private API means that independent reproduction is not possible today in any case.
Why Meta closed the open-source gates
Meta’s Llama series, from the first weight release in February 2023 through Llama 4 in April 2025, made the company the defining force in open-weight AI. The Llama 3.3 70B model became the default choice for organizations needing strong performance on infrastructure they controlled. Across all versions, the Llama ecosystem accumulated 1.2 billion downloads. No competitor approached that scale in the open-weight category.
That position eroded through 2025. Alibaba’s Qwen 3.6-Plus matched Llama 4’s coding performance at roughly $0.29 per million input tokens. DeepSeek V3.2 pushed below that. More consequentially, Chinese labs began setting the pace of architectural innovation that Meta had previously defined. By late 2025, Chinese models accounted for 41 percent of downloads on Hugging Face. The open-weight leadership had transferred.
Muse Spark is not open source. Wang addressed this directly: the new architecture and training methodology needed validation at scale before the underlying technology could be published. Meta says it hopes to open-source future Muse models. The distance between “hopes to release open-source future versions” and the Llama-era practice of shipping the same weights developers actually use is significant. Llama’s open-source commitment was a competitive weapon, driving ecosystem adoption and creating switching costs for developers who built production systems on it. Closing the gates on Muse Spark removes that weapon from the arsenal at the moment Meta faces its sharpest open-weight competition from abroad.
The strategic logic is that Meta needs time to validate the Muse architecture at larger scales before sharing the design. If Muse Spark’s 10x compute efficiency advantage holds across the scaling curve, and Meta can build a Muse model that leads on quality benchmarks before publishing its architecture, the open-source release becomes a fait accompli rather than a competitive giveaway. The risk is that the 12 to 18 months that scenario requires is long enough for Alibaba and DeepSeek to independently converge on similar architectural improvements. Open-source strategy works when you are leading. Meta is not leading right now.
What the model cannot do yet
Muse Spark accepts text, image, and voice inputs. It produces text output only. Image generation is planned but not shipped. The Vibes AI video generation feature in the Meta AI app currently runs on models from Black Forest Labs, not Muse Spark. The API is in private preview, meaning organizations that want to build with Muse Spark cannot do so today.
Contemplating mode is not available in the standard interface by default. Users toggle between a quick-answer mode and an extended reasoning mode. The latency difference is real: parallel agent execution requires coordination overhead, and problems that decompose cleanly into independent subproblems benefit most. Problems that require serial reasoning chains, where each step depends on the result of the previous one, gain less from parallelism and in some cases show degraded coherence when synthetic subagent outputs are merged. Meta does not publish a characterization of which task types benefit from Contemplating mode versus which degrade.
The two capability areas Meta explicitly flags as requiring continued improvement are long-horizon agentic tasks and coding workflows. These are exactly the categories where Claude Opus 4.6 and GPT-5.4 have the widest leads. Muse Spark’s 4th-place benchmark position reflects this gap honestly.
What the next nine months determine
Meta structured the Muse Spark release as step one of a multi-phase scaling program. Wang’s statement was direct: “This is step one. Bigger models are already in development.” The stated plan is to use Muse Spark as architectural validation, confirm the scaling law holds, then build larger Muse models using the same training methodology. Zuckerberg separately committed to releasing future Muse models as open source, but with no timeline. Meta’s capital expenditures on AI infrastructure in 2026 are projected at between $115 billion and $135 billion, roughly twice the prior year. The computational resources exist. The question is whether the architecture scales as efficiently as the small-model results predict.
For developers, the relevant signal from today is not benchmark position. It is that Meta has validated a new multimodal reasoning architecture with competitive performance at small scale and high compute efficiency. Google’s Gemma 4 and Meta’s Llama 4 currently define what is available in open-weight reasoning models. When Muse family models arrive as open weights, the architectural choices Meta made in this release, particularly the unified multimodal representation and the parallel-agent scaling approach, will determine whether they can compete with what Alibaba and DeepSeek are releasing on the same timeline.
What is clear today: Meta shipped a fourth-place reasoning model with a novel inference architecture, reversed its open-source policy, and declared the release a foundation rather than a destination. Whether that foundation can support what comes next depends on how well a scaling law measured on small models holds when applied to systems ten or fifty times larger. That question does not have an answer yet.