Meta Muse Spark 1.2 and Muse Code: a 54-point step that bets on long-horizon coding over raw benchmark supremacy
Technical background: agentic work has become the new frontier axis
In the second half of 2026, the competition axis for frontier LLMs has shifted from "whose raw benchmark score is highest" to "who can carry realistic agentic workloads". Claude Opus 5, GPT-5.6 Sol and Kimi K3 have all refreshed the upper bound on GDPval-AA v2 and Terminal-Bench, and "general chat" has been compressed from a decisive battleground into an entry ticket. Meta Superintelligence Labs launched Muse Spark 1.0 (43 on the AA Index) in April, pushed to 1.1 (51) in July, and on August 5 released Muse Spark 1.2 (54) together with the terminal coding agent Muse Code. The bet is to win back share on the narrower but commercially more valuable axis of "code + long-horizon tasks". The independent numbers behind Muse Spark 1.2 come from Artificial Analysis (published 2026-08-05), which moves this update from a one-sided announcement into externally verifiable hard data.
What Muse Spark 1.2 actually changes: three deltas and one trade-off
1. Agentic knowledge work closes the gap, but the cost curve moves with it
On Artificial Analysis's Intelligence Index, Muse Spark 1.2 (xhigh) lands at 54 — +3 over 1.1 and +11 over 1.0. It is effectively tied with SpaceXAI in third place among US labs, and within a point of GPT-5.5 (xhigh, 55) and Grok 4.5 (high, 54). It is only narrowly behind Claude Opus 5 (max, 61), Claude Fable 5 (max w/ fallback, 60), GPT-5.6 Sol (max, 59) and Kimi K3 (max, 57). Most of the lift comes from agentic evaluations: GDPval-AA v2 Elo jumped +260 (1371 → 1631, #5 among all benchmarked models and ahead of Claude Opus 4.8's 1588); Terminal-Bench v2.1 rose +2 points (78% → 80%); τ³-Banking rose +2 points (25% → 27%). The bill is also larger: per-Intelligence-Index-task cost moved from $0.29 to $0.40 at Meta's unchanged $1.25/$4.25 per 1M token pricing, driven by ~53% more input tokens and ~36% more output tokens per task, concentrated in GDPval-AA v2.
2. Muse Code turns "long-horizon tasks + subagent orchestration" into the default behaviour
Meta's release blog describes Muse Code as an asynchronous background-agent model rather than a classical "single main agent with ad-hoc dispatch". Each session keeps a small set of persistent background agents (Photon Sphere, Embervault, Avo Lawn) that remain alive across tasks, take next steps on their own and decide when to report back to the main agent. The intent is to remove redundant information gathering, lower latency and avoid the constant re-prompting that long multi-step tasks normally require. Every model call, tool run, approval and edit is appended to a local event log, making the runtime replay-exact and restart-safe: after a crash the agent resumes precisely where it stopped. This design quietly deletes "the long task crashed, start over" from the default assumptions of coding agents. Three bundled skills — /plan, /grill, /goal — cover "produce an approval-gated plan", "stress-test that plan until it holds" and "drive toward the specified goal".
3. Co-training with Muse Code + a "self-improvement loop" is the training-side headline
The release explicitly states that Muse Spark 1.2 was co-trained with the Muse Code harness: rejection-sampled harness trajectories, recipe optimisation for goals / compaction / subagents, and the integration of the Muse Code toolset so the model performs best when paired with Muse Code. A second training move uses Muse Spark 1.1 itself to generate hard coding environments and instruction-following templates, then to grade candidate solutions against them — producing a scalable training corpus for 1.2. The Case Study in the blog pushes this further: the team ran Muse Spark 1.2 over 1,000+ tool calls (up to 24 hours) to iteratively optimise GPU kernels on NVIDIA Hopper, targeting KDA and MLA kernels. The baseline was the FLA Triton implementation; models were forbidden from importing third-party kernel libraries and had to write the algorithm themselves. Muse Spark 1.2 paired a chunk-parallel preparation kernel with a sequential inter-chunk scan for KDA, and a two-kernel Triton pipeline for MLA that reuses the shared KV latent as both K and V.
4. The trade-off: slight regression on scientific reasoning and a doubled-down abstention strategy
SciCode dropped 2 points (58% → 56%); Humanity's Last Exam dropped 1 point (45% → 44%); CritPt rose 3 points (15% → 18%). More striking is the AA-Omniscience result: the score rose 18 → 22, the hallucination rate fell 10 points (38% → 28%), but the attempt rate dropped from 82% to 67%, and accuracy slipped 41% → 38%. For the second release in a row Meta is betting that "the model should refuse when it doesn't know" is a feature, not a regression — and is willing to pay for it in raw answer rate.
Pricing and context (carried over from 1.1)
The model retains the 1M-token context window and the same pricing as Muse Spark 1.1: $1.25 / $4.25 per 1M input / output tokens, with cache hits at $0.15 per 1M. It is available at launch on Meta's first-party API (Meta Model API) and inside Muse Code. Sources: https://research.meta.ai/blog/introducing-muse-code-and-muse-spark-1-2 and https://artificialanalysis.ai/articles/muse-spark-1-2.
Why Meta is using long-horizon coding + agent orchestration to break into the 54-point tier
Putting Muse Spark 1.2 into the 2026-H2 coordinate system, this is not a "highest score wins" release. Claude Opus 5, GPT-5.6 Sol, Fable 5 and Kimi K3 are all still ahead of it. Meta's choice, however, is legible: it is not chasing GPT-5.6 Sol on the general-chat red-ocean axis; it is binding "agentic tasks + long-horizon coding + its own harness" into a tight loop. Two signals are worth tracking.
The first is "cost goes up, and that is OK". Muse Spark 1.2's per-task cost rose ~38% ($0.29 → $0.40), but its per-task scores rose more — this is "higher score is worth more tokens" being put back into the product decision. Looking only at token price, Muse Spark 1.2 is still cheaper per task than GPT-5.6 Sol ($0.51), Kimi K3 ($0.86) and GPT-5.5 ($1.18), and remains a cost-efficient option at the 54+ cluster; but versus GPT-5.6 Sol (medium, $0.39) the gap is only $0.01. Meta is clearly normalising higher token usage in agentic workflows in exchange for higher success rates.
The second is "self-improvement loop + co-training" being written into the public release narrative. Meta used 1.1 to generate hard coding environments and instruction templates, then used 1.1 to grade candidate solutions, and folded that output back into 1.2's training data. This is reminiscent of Anthropic's Constitutional-AI self-critique loop; Meta's version pushes it onto the more "engineering" axis of coding benchmarks + long-horizon agents, where it directly meets commercial demand.
The side effect has to be named: factual reliability is sliding. AA-Omniscience attempt rate dropped 82% → 67% and accuracy 41% → 38% — Meta is doubling down, for the second evaluation cycle in a row, on "the model prefers to abstain". If Muse Code and similar long-horizon agents keep being trusted to make their own decisions in production (writing code, running tests, tuning kernels), "will the model fabricate a plausible-looking but factually wrong intermediate conclusion" stops being an academic question and becomes a regression-quality risk. Meta has not offered a new mitigation for this in the release.
So the real bet of Muse Spark 1.2 is: while GPT-5.6 Sol and Claude Opus 5 are holding the general-purpose ceiling, Meta will eat the smaller but more commercially immediate lane of "programming + agents + long tasks" — chasing only to 54 points, but spending every point on the abilities that translate most directly into willingness to pay. If this path works, the H2-2026 LLM competition may no longer be "whose score is highest", but "whose model runs most reliably inside its own harness and on its own evaluations".
(Original Meta AI Research release: https://research.meta.ai/blog/introducing-muse-code-and-muse-spark-1-2; Artificial Analysis independent evaluation: https://artificialanalysis.ai/articles/muse-spark-1-2)