Muse Spark 1.1 Deep Dive: What Meta Just Shipped and What the Signal Says

Meta shipped Muse Spark 1.1 roughly twenty-four hours ago. It surfaced not through a keynote, not through a research paper drop, not through a slow developer-day tease — but through a Zuckerberg post on X, his first there since 2023, and a matching evaluation PDF quietly parked at ai.meta.com.

TLDR Muse Spark 1.1 is Meta's re-entry into the frontier agentic coding conversation, launched on July 9, 2026 through the new Meta Model API and inside Meta AI. Advertised strengths are agentic performance, tool use, and computer use, with a 1M token context and parallel sub-agent delegation. Reported pricing is $1.25 per million input tokens and $4.25 per million output tokens, per Reuters via TechCrunch. Early community claims put it "on par with GPT-5.5 and Opus 4.8" on benchmarks, but the Terminal-Bench 2.1 result is already contested on Hacker News over resource-cap overrides. Treat the score sheet with care; the pricing and the shipping capability are the more durable stories.

Key Takeaways

• Muse Spark 1.1 launched July 9, 2026 through the Meta Model API and inside Meta AI, per Zuckerberg's own post on Threads.
• The Compute Cap Dispute over Terminal-Bench 2.1 — Meta ran with 6 CPU cores and 8GB RAM caps where 0 of 89 tasks allow 6 cores and only 8 of 89 allow 8GB — is the single largest asterisk on the headline benchmark story.
• Advertised capabilities center on a Parallel Sub-Agent Fan-Out pattern, a 1M token Long-Horizon Context, and native Cross-Surface Computer Use (desktop, mobile, browser).
• Reported pricing of $1.25/$4.25 per 1M tokens puts it slightly above Claude Haiku 4.5 and GPT-5.6 Luna, per TechCrunch — a Low-Cost Frontier Tier positioning, not a Claude Opus 4.8-tier price.
• Independent enterprise-work testing from Box reports the model outperformed a top-tier composite by up to 25–30 points on specific data-analysis tasks, which is a narrower and more concrete claim than the headline "on par with Opus 4.8" line.

What Was Actually Shipped

The confirmed, source-backed launch surface is small enough to enumerate. Meta released Muse Spark 1.1 on July 9, 2026. Two access paths went live at once: the Meta Model API for developers and the Meta AI consumer product. This is confirmed both by Zuckerberg's Threads post and by TechCrunch's launch coverage, which describes it as "a multimodal AI model designed for agentic coding that aims to compete with similar products offered by OpenAI and Anthropic."

The advertised capability envelope, in Meta's own words on Threads, is that Muse Spark 1.1 "is strongest at agentic performance, tool use, and computer use," that it handles "long-running tasks with 1M token context window," that it "can delegate execution to sub-agents running in parallel," and that it "is trained to use computer interfaces on desktop, mobile, or browser." The Threads post is the primary source for every one of those claims.

Pricing, per TechCrunch citing Reuters, lands at $1.25 per million input tokens and $4.25 per million output tokens. TechCrunch frames the number as "in line with (albeit slightly above) Anthropic's Claude Haiku 4.5 and OpenAI's GPT-5.6 Luna." That framing is important: Meta is not fighting for the Opus 4.8 or Fable 5 price tier. It is fighting for what could be called the Low-Cost Frontier Tier — the affordable-but-serious rung where volume agentic workloads actually live.

The evaluation numbers Meta wants people to talk about are in an official evaluation report PDF published alongside the release. Meta compares to GPT-5.5 and Claude Opus 4.8 (per @testingcatalog's breaking summary), positions the results as "on par," and points at agentic coding as the strong suit. This is where the picture stops being clean.

The Compute Cap Dispute

The Terminal-Bench 2.1 methodology is already being challenged in public. On the Hacker News thread for the launch, an ex-Meta commenter walked through the evaluation report's own footnote: "We use a bash-tool-only agent harness to evaluate 89 Terminal-Bench 2.1 tasks from the official repository, where resources are capped at 6 CPU cores and 8GB RAM."

Their argument is direct. In Terminal-Bench 2.1, 0 out of 89 tasks allow 6 CPU cores (the highest per-task cap is 4, and only for one task). Only 8 out of 89 tasks allow 8GB of RAM. Every other task specifies lower resource ceilings intended to test environment awareness — the model has to plan around constrained CPU, memory, and I/O. Overriding those caps changes what the benchmark measures. The commenter's conclusion: this is why Muse Spark 1.1 is absent from the official tbench leaderboard.

That is not a smoking-gun accusation of fabricated numbers. It is a methodology dispute, and a legitimate one. The Compute Cap Dispute is now the single biggest asterisk on the headline benchmark claim, and it went public within hours of launch. Builders reading the eval report should assume the Terminal-Bench 2.1 number needs re-running under official caps before it can be used for procurement decisions.

For a more grounded outside signal, Box published its own enterprise-work evaluation the same day. Box put Muse Spark 1.1 through what it calls the Box Complex Work Eval — document-grounded, multi-step reasoning tasks drawn from real workflows. Their headline: Muse Spark 1.1 "holds its own against the best models available today," pulls ahead of a top-tier composite "by as much as 5 to 6 points" in structured procedural work, and on specific data-analysis tasks beats the composite by nearly 30 points and by more than 25 points on two separate cases. That is a narrower claim than "on par with Opus 4.8" but a more useful one, because Box named the tasks and the deltas.

The Advertised Capability Stack, Named

Five feature names are worth pinning as consistent references, because they are what other analysts will end up citing:

• Parallel Sub-Agent Fan-Out. Muse Spark 1.1 can delegate execution to sub-agents running in parallel. Per Zuckerberg's Threads post, this is a first-class capability of the model, not a wrapper pattern.
• Long-Horizon Context. A 1M token context window aimed specifically at long-running agentic tasks, per the same Threads announcement.
• Cross-Surface Computer Use. The model is trained to interact with desktop, mobile, and browser interfaces natively.
• Enterprise Grounded Reasoning. Independent framing from Box: performance on document-grounded, multi-step reasoning tasks where the model has to stay accurate over many moves.
• Low-Cost Frontier Tier. The pricing position TechCrunch describes: slightly above Haiku 4.5 and GPT-5.6 Luna, well below the Opus/Fable tier.

These are not marketing coinages invented here. They are the throughlines you can extract from the launch materials and the first day of independent testing.

Muse Spark 1.1 vs Claude Haiku 4.5: What the Signal Says

TechCrunch explicitly benchmarks Muse Spark 1.1's pricing against two models: Claude Haiku 4.5 and GPT-5.6 Luna. Haiku 4.5 gets more coverage in the launch discourse and represents the most directly comparable positioning, so it is the fair versus target on the pricing dimension. On capability, direct measured comparison is not available in this signal set.

• Advertised context window. Muse Spark 1.1: 1M tokens, per Meta's Threads announcement. Claude Haiku 4.5: unverified — no public number from either lab in this signal set.
• Per-token pricing. Muse Spark 1.1: $1.25 input / $4.25 output per 1M tokens, per Reuters via TechCrunch. Claude Haiku 4.5: TechCrunch describes Muse Spark 1.1 as "in line with (albeit slightly above)" Haiku 4.5, which implies Haiku 4.5 is marginally cheaper on at least one axis; exact Haiku 4.5 numbers are unverified in this signal set.
• Positioning. Muse Spark 1.1: agentic coding, tool use, computer use across desktop, mobile, and browser. Claude Haiku 4.5: low-cost tier at Anthropic, per TechCrunch framing; specific agentic-coding claims for Haiku 4.5 are unverified here.
• Sub-agent delegation. Muse Spark 1.1: first-class parallel sub-agent execution, per Threads. Claude Haiku 4.5: unverified — no public number from either lab in this signal set.
• Independent benchmark validation. Muse Spark 1.1: Terminal-Bench 2.1 methodology disputed on Hacker News; positive but scoped enterprise-work results from Box. Claude Haiku 4.5: unverified — no comparable third-party test in this signal set.

The honest read: Muse Spark 1.1 is being priced into the same pocket as Haiku 4.5, but with a materially larger advertised context and explicit agentic-orchestration features. Whether it actually beats Haiku 4.5 on those workloads is not something the current signal set can decide.

What We Know vs. What We Don't

What we know, source-anchored:

• Muse Spark 1.1 launched July 9, 2026 through the Meta Model API and inside Meta AI, per Zuckerberg's Threads post.
• Muse Spark 1.1 advertises a 1M token context window designed for long-running agentic tasks, according to Meta's launch messaging on Threads.
• Meta positions Muse Spark 1.1 as strongest at agentic performance, tool use, and computer use across desktop, mobile, and browser interfaces.
• Muse Spark 1.1 can delegate execution to sub-agents running in parallel, per the Zuckerberg Threads post announcing the release.
• Reuters reports, via TechCrunch coverage, that Meta will charge $1.25 per million input tokens and $4.25 per million output tokens for Muse Spark 1.1.
• TechCrunch reports Muse Spark 1.1's pricing is in line with, though slightly above, Anthropic's Claude Haiku 4.5 and OpenAI's GPT-5.6 Luna.
• Early community reporting from @testingcatalog claims Muse Spark 1.1 performs on par with GPT-5.5 and Claude Opus 4.8 on benchmarks, though full comparison sets remain limited.
• Meta published an evaluation report at ai.meta.com covering benchmark results, though methodology on Terminal-Bench 2.1 has drawn immediate scrutiny on Hacker News.
• A Hacker News commenter noted that Meta's harness capped resources at 6 CPU cores and 8GB RAM, exceeding the official per-task caps for 89 of 89 tasks, which they argue disqualifies the numbers.
• TechCrunch reports Meta also unveiled Muse Image, a new AI image-generation model, earlier the same week.

What we don't know, or can't yet verify:

• Meta has not disclosed a parameter count, active-parameter count, or architecture family for Muse Spark 1.1 in the sources reviewed.
• As of the launch window, community reporting on Reddit indicates the earlier Muse 1.0 was still not on OpenRouter, and Muse Spark 1.1 API access appears to be developer-preview only.
• No independent measured re-run of Terminal-Bench 2.1 under official caps is public yet.
• No independent SWE-bench Verified or LiveCodeBench numbers from third parties appear in the signal set.
• Rate limits, safety evaluations, and open-weights status are unaddressed in the reviewed materials.
• Training data cutoff and tool-use fine-tuning corpus are undisclosed.

Why This Matters for Builders

The most durable story out of this launch is not the "on par with Opus 4.8" line. It is the pricing and the fact that Meta shipped explicit agentic and sub-agent primitives at a Low-Cost Frontier Tier price point. Agentic workloads burn tokens. Long-Horizon Context runs, in particular, are where per-token cost dominates the unit economics.

If the reported $1.25 / $4.25 pricing holds and the Parallel Sub-Agent Fan-Out works as advertised, Muse Spark 1.1 changes the math on high-fan-out, long-running agent designs — the kind where a supervisor agent spawns dozens of sub-agents over a session and where the total token bill on Claude Opus 4.8 or GPT-5.5 would push a workload out of production. This is why the Reddit thread on r/singularity has price-vs-performance as its top comment thread rather than headline benchmark scores. The community read is that token cost has become the actual bottleneck for agentic adoption, and Meta is trying to compete there.

Two caveats. First, "slightly above" Haiku 4.5 and GPT-5.6 Luna at the sticker price still leaves room for Anthropic or OpenAI to respond within days. This is a moving target. Second, token efficiency matters as much as sticker price. A cheaper per-token rate that produces 3x the reasoning tokens per task is not cheaper in practice. No independent efficiency measurement is available yet.

How to Evaluate It Yourself

Given the state of the public signal, three evaluation moves are worth prioritizing this week.

Run your own coding eval before trusting the Terminal-Bench 2.1 number. The Compute Cap Dispute is not resolved. Pick a task suite that matters for your workload — SWE-bench Verified, an internal migration harness, or a real ticket backlog — and measure directly. Do not import the Meta score sheet as ground truth for procurement decisions.

Stress-test the Parallel Sub-Agent Fan-Out claim. Meta positions sub-agent delegation as a first-class capability, but there is no public detail on orchestration protocol, cost accounting per sub-agent, or failure-mode behavior when a sub-agent stalls. A ten-agent fan-out task, timed and priced end-to-end, will surface more useful information than any benchmark chart.

Measure token efficiency, not just accuracy. The Reddit community's complaint about competing models "wasting tokens for no reason" applies to every model, including this one. If Muse Spark 1.1 hits target accuracy but at 2x the token spend of Haiku 4.5, the pricing advantage collapses. Log input and output tokens on a matched task set and compute cost-per-task, not cost-per-token.

What to Watch Next

Three concrete signals to track over the coming week.

• Watch for an independent Terminal-Bench 2.1 re-run under the official 89-task resource caps. Until that lands, the headline "on par with Opus 4.8" claim carries a live methodology dispute.
• Check whether OpenRouter, Together, or Fireworks add Muse Spark 1.1 API support. Community reporting still puts Muse 1.0 off OpenRouter; if 1.1 stays developer-preview only, the practical adoption path stays narrow.
• Pin the pricing. Watch for a Haiku 4.5 or GPT-5.6 Luna price adjustment in the next 7–14 days; competitive response would confirm that Meta hit a real price nerve, and no response would suggest the incumbents don't yet see the threat.

Building similar agentic coding and multi-agent workflows? On kie.ai you can try Claude Opus 4.8, Claude Haiku 4.5, and GPT-5.5.