Meta is back in the AI race

A year ago, Meta could not launch an AI model without starting an argument about whether its benchmarks were real. Last week it released a coding agent built to work for 24 hours. Five days later, it put an Apache 2.0 model on Hugging Face that can run an agent on your own machine.

Muse Glimmer is not Meta's smartest model. That is exactly why it matters. It is a 30B-class distillation of Muse Spark, tuned for tools, coding and long-running tasks, and small enough to fit inside the local AI ecosystem. Spark chases the frontier. Glimmer puts the same agent thesis on hardware people can own.

Meta is not leading the AI race. It has done something almost as consequential: it has made itself impossible to dismiss.

The failure that made the comeback possible

Llama 4 arrived on April 5, 2025 with exactly the kind of launch Meta had learned to stage well. Scout promised a 10-million-token context window. Maverick paired 17 billion active parameters with 128 experts. Behemoth, a roughly two-trillion- parameter teacher model, was previewed as one of the smartest models in the world. Scout and Maverick were available as open weights on day one.

Then people used them. The public models felt weaker than the launch charts implied, especially for coding. More damagingly, the version of Maverick on LMArena was an experimental chat-tuned variant, not the downloadable model most people thought they were judging. Meta disclosed that detail, but not clearly enough to prevent the obvious conclusion. Meta denied artificially boosting the scores; LMArena said the customized submission should have been made clearer.

The distinction matters. There was no clean proof that every benchmark had been fabricated. There was something worse for a model lab: users stopped trusting the comparison. Meta's longtime chief AI scientist Yann LeCun later said the results had been “fudged a little bit.” Behemoth was delayed and never became the open flagship the launch had promised.

Llama 4 was not useless. It was a capable, efficient open model family wrapped in claims it could not carry. That gap between product and story is what broke Meta's momentum.

The $14.3 billion reset

Zuckerberg did not respond with a normal reorganization. In June 2025, Meta made a $14.3 billion investment in Scale AI for a 49% stake and recruited its founder, Alexandr Wang, to become Meta's first Chief AI Officer. Wang took charge of the newly formed Meta Superintelligence Labs. Meta then recruited aggressively across OpenAI, Anthropic and Google DeepMind while rebuilding its training stack.

Calling the whole investment an executive signing bonus is catchy and wrong. Meta bought a large stake in a strategically important data company and got Wang as the leader of its model reset. Still, the size of the deal made the mandate obvious: incremental improvement was not enough.

Muse Spark was the first receipt. Meta said MSL rebuilt its pretraining stack, architecture, optimization and data curation in nine months. The original model was deliberately small, fast and natively multimodal, with tool use, visual reasoning and parallel-agent orchestration. Meta also did something unusually useful in its launch post: it named the weak spots. Long-horizon agents and coding were not yet good enough.

The next two releases attacked precisely those weaknesses. That is why the cadence matters. It looks less like random shipping and more like a team working through a measured list of failures.

Six releases, two tracks

Muse Image is easy to treat as a side quest, but it reveals the common design. Instead of mapping a prompt straight to pixels, the model can search, write code, critique a draft and try again. Meta reported that Muse Image ranked second on Arena for text-to-image and editing on July 5; Muse Video ranked third in its early preview. The point is not that every Muse model is an agent. It is that MSL is building tool use and test-time work into the family rather than bolting them on after training.

Muse Code makes that thesis concrete. It is a terminal agent that plans changes, edits large repositories and validates the result. Persistent background agents stay alive through a session instead of starting cold for every subtask. An append-only local event log records model calls, tool runs, approvals and edits, allowing a long job to resume after a crash. Meta says it tested one kernel- optimization run across more than 1,000 tool calls and up to 24 hours.

Those are system features, not magical properties of the language model. That is exactly the point. The coding race is increasingly model plus harness plus tools, and Meta is now training both sides together.

Muse Glimmer changes the argument

On August 10, Meta opened the weights for Muse Glimmer 30B under Apache 2.0. The name is soft; the intent is not. Glimmer is a 29.6-billion-parameter dense model distilled from Spark, with a vision encoder, a 131K-token context window and a training mix built around tools, coding and multi-step agents.

The practical trick is compression. Meta's 4-bit language model comes in under 20GB, leaving room on a 24GB or 32GB machine for the vision encoder, KV cache and a small speculative-decoding model. Meta reports 233 tokens per second on an RTX 5090 with that drafter, a 3.1x speedup over normal decoding. On an M5 Max, it reports 50 tokens per second. Those are vendor measurements, but the weights are public now, so they will not stay vendor-only claims for long.

The benchmark story is strong but not clean enough for a victory lap. In Meta's high-reasoning tests, Glimmer scored 75.5 on MCP Atlas and 51.2 on SWE-Bench Pro, ahead of the tested Gemma 4 31B and Qwen 3.6 27B variants. Qwen still led on TerminalBench, OSWorld and GDPval-AA. That is the useful read: Glimmer looks very good for its size, especially when tools are involved, but it does not erase the rest of the open-model field.

What it changes is where the agent can live. A local model can work over private code, documents, screenshots and home systems without sending the whole job to a cloud API. It can also keep running when the network is bad or the API budget is gone. The first community reports were predictably messy, with loader errors and integrations still landing, but that mess is part of an open release. People can inspect the failure instead of waiting for a vendor to fix it behind an endpoint.

Zuckerberg added a larger promise: Spark 1.2 weights are coming “soon.” If that happens, Meta will have reopened more than the small-model lane. Until the files and license exist, though, Spark is still a closed model. A post is not a release.

What the benchmarks actually say

Muse Spark 1.2 scores 54 on the current Artificial Analysis Intelligence Index, up from 51 for 1.1 and 43 for the original model. That puts Meta near GPT-5.5 and Grok 4.5, but behind Claude Opus 5 at 61, Claude Fable 5 at 60, GPT-5.6 Sol at 59 and Kimi K3 at 57. Competitive, yes. Best, no.

The table gives the honest shape of the release. Most of the three-point gain comes from agents doing realistic knowledge work. GDPval-AA v2 jumped 260 Elo, taking Muse Spark 1.2 to fifth among models Artificial Analysis had tested. The science picture barely moved. SciCode and Humanity's Last Exam both slipped slightly.

Reliability improved in a stranger way. On AA-Omniscience, the model's hallucination rate fell from 38% to 28%, but its attempt rate also fell from 82% to 67% and raw accuracy slipped from 41% to 38%. Muse got better at knowing when not to answer. That is valuable in production, but it is not the same thing as knowing more.

Meta's own Muse Code chart reports 82.9% on Terminal-Bench 2.1, behind Claude Opus 5 at 86.7%. Artificial Analysis measured 80%. Neither number has to be fraudulent. Agent benchmarks measure the model inside a harness, and Meta co-trained 1.2 with Muse Code. Change the scaffolding, tool policy or reasoning budget and the score moves. After Llama 4, however, Meta has earned a higher burden of disclosure. The independent 80% is the safer comparison; the 82.9% shows what Meta's full stack can do in Meta's setup.

Zuckerberg is not trying to win Chatbot Arena

Zuckerberg's phrase for the strategy is “personal superintelligence.” It sounds grandiose because it is. But beneath the name is a specific product thesis: the winning assistant will know your goals, understand your context and stay with you across the day. In his July 2025 letter, he framed the choice as personal empowerment versus AI that replaces “large swaths of society.” He expects glasses that can see and hear what you do to become a primary computing device.

This is where Meta's position differs from that of a model-only lab. It reported 3.56 billion daily users across its family of apps in March 2026. Muse Spark can move from a benchmark into WhatsApp, Instagram, Facebook, Messenger, Meta AI and glasses without waiting for a developer ecosystem to form. In July, Meta added agent-like features that can connect to email and calendars, create recurring briefings, conduct research and make slides.

Zuckerberg's Muse Spark 1.1 post was revealingly practical: strong agents and multimodality “at a very low price.” Meta priced the API at $1.25 per million input tokens and $4.25 per million output tokens, with cached input at $0.15. Artificial Analysis estimates that 1.2 costs about $0.40 per Intelligence Index task. Meta can tolerate thin model margins because its main business sits elsewhere. OpenAI and Anthropic cannot ignore that pressure.

The uncomfortable mirror image is privacy. An assistant becomes more useful as it knows more about you; many people trust Meta less for exactly the same reason. The data advantage and the trust problem are not separate features of this strategy. They are the same feature viewed from opposite sides.

Wang's argument is speed, agents and cost

Wang has been more disciplined than the “superintelligence” branding around him. He called Muse Spark 1.1 “industry-competitive,” not industry-leading, and said agentic performance and tool use were where Meta was strongest. His posts focused on active context management, parallel subagents and the model knowing when to script a task instead of clicking through it.

That language describes a workhorse, not an oracle. It also matches the releases. April's model proved the new training stack worked. July's model made it cheap and available to developers. August's model closed part of the agent gap and arrived with a harness designed around it. Meta says larger and much more capable models are still on the way.

Wang's most persuasive claim is therefore not a benchmark boast. It is the loop: ship, measure, target the weakness, ship again. Meta went from Spark 1.0 to 1.2 in less time than many companies take to rename a preview. Glimmer extends that loop beyond Meta's API: distill the flagship, tune it for a specific job, then give the ecosystem the weights.

The reaction: excitement, then the trust bill

The first Muse launch produced a rare burst of genuine surprise. Logan Kilpatrick said he was excited to see Meta back in the game. Investor Haseeb Qureshi wrote that reports of Meta's death had been exaggerated: “It's a race again.” Developers shared visual-coding demos that did things they had not seen from other models. Meta's stock rose 6.5% after the April launch, a market vote that the reset had produced something tangible.

The skepticism was just as specific. François Chollet argued that the first Muse looked over-optimized for public benchmarks. After 1.1, engineer and writer Gergely Orosz said the model looked impressive on paper but warned that developer trust takes years, especially for a company with a thin record in dev tools. Ethan Mollick offered the most balanced description: Meta had rejoined the “near-frontier” while helping create a new class of cheap, fast, closed models.

Early Muse Code reaction follows the same split. Some developers report startling price-performance and strong repo-wide edits. Others describe wandering reasoning, over-eager package installation and weak results outside Meta's benchmark harness. A recurring objection is simpler: they do not want to give Meta a private codebase.

Glimmer changed the mood almost immediately. Local-model developers celebrated the Apache 2.0 license, started quantizing it and argued over the Qwen comparisons. They also hit day-one tooling problems. That mix of hype, skepticism and public debugging is healthier than a closed launch because the argument can move from screenshots to reproducible tests.

The old skepticism has not disappeared. It is the bill for Llama 4 and Meta's broader reputation. Another strong launch will help. A year of reliable tools and releases will help more.

The open-weight bargain is back, with an asterisk

Llama made Meta the unlikely champion of open-weight AI. Developers could download the models, fine-tune them and run them wherever they wanted. When the first Muse releases arrived behind products and APIs, it looked like that chapter had ended. Glimmer makes that conclusion obsolete.

The emerging shape is a two-track strategy. Spark is the frontier system: larger, closed for now and tightly connected to Meta's API, agents and consumer products. Glimmer is the edge system: smaller, open-weight and designed to be adapted by a local ecosystem Meta does not control.

“Open source” still deserves precision here. Meta released model weights and supporting artifacts under a permissive license. It did not release the training data or a complete recipe for recreating Glimmer. Open-weight is the more accurate term, and it is still a meaningful release.

Spark 1.2 is the real test. Opening a compact distillation is useful. Opening the current flagship would be a much larger commitment. Zuckerberg has said that is coming, but Meta should get credit when the artifact ships, not before.

Strategically, this looks very Meta. Keep a first-party frontier stack for products used by billions, while making local inference cheap and abundant enough to pull developers toward the Muse family. Meta can win from distribution and from commoditization at the same time.

So, is Meta really back?

Yes, with a narrower meaning than the headline usually carries.

Meta is back because a model buyer now has to consider it. At 54 on the current Intelligence Index, Muse Spark 1.2 is close enough to the frontier to compete on price, speed and task fit. Its agentic knowledge-work jump is substantial. Its one-million-token context window and low cached-input price make it interesting for long-running systems. Muse Code shows Meta understands that useful coding agents are built, not merely prompted.

Meta is not back because it solved intelligence. The best models still score higher. Muse 1.2 gained by spending more tokens. Its scientific reasoning was flat. Glimmer's launch numbers still need independent replication, and Spark 1.2 remains closed until the promised weights actually appear. Developers have rational reasons to distrust both the company and its launch charts.

The deeper advantage is that Meta does not need to win every benchmark. It needs models good enough to make its distribution, data, infrastructure and price decisive, then open models good enough to make its ecosystem hard to avoid. The company plans to spend roughly $125 billion to $145 billion on capital expenditure in 2026 and can put a new model in front of billions of people almost overnight. Few labs can answer that combination.

Frequently asked questions

Sources and further reading

Benchmark snapshots change quickly. For live model pricing and performance, use the WhatLLM model explorer. For the larger open-versus-closed context, read The open-model gap is not one gap.