Meta launches Muse Code AI coding agent

Muse Code's standard pricing lands at $1.25 per million input tokens and $4.25 per million output tokens, but Meta also offers a steeply discounted contributor tier at $0.10 per million input and $0.20 per million output tokens, roughly 20 times cheaper ^[1]. The catch is that the contributor tier requires developers to let Meta use their prompts and completions to train future models, and Meta backs the discount with much tighter throughput limits: 60 requests per minute and 2.1 million tokens per minute, versus 3,000 requests per minute and 4 million tokens per minute on the standard tier ^[1].

The tradeoff has not gone unnoticed. A MacRumors forum thread dedicated to the pricing split shows mostly skeptical sentiment, with a number of commenters arguing the discount is not steep enough to justify handing Meta training rights over their code, alongside a smaller group willing to accept the exchange ^[2]. That data-hungry posture is not new for Meta: the company has said it required thousands of internal engineers to use Muse Code weekly, with roughly 7,000 active internal users producing more than 800 fixes that fed back into the model, according to Meta's own account ^[3]- a precedent that suggests the contributor tier is less an experiment than an extension of a data flywheel Meta already runs in-house.

On Meta's chosen benchmarks, Muse Spark 1.2 posts real gains over its predecessor: 82.9% on Terminal-Bench 2.1 and 59.3% on DeepSWE v1.1, up from 76.2% and 53.0% for Muse Spark 1.1 ^[4]. That edges out OpenAI's GPT-5.6 Terra in Codex (81.8% on Terminal-Bench 2.1) and xAI's Grok 4.5 in Grok Build (81.6%) ^[4].

But the same chart undercuts Meta's positioning against the actual category leader: Claude Opus 5 running Claude Code scores 86.7% on Terminal-Bench 2.1 and 65.0% on DeepSWE v1.1, beating Muse Spark 1.2 on both, and Meta's own internal 440-pull-request test reportedly shows Claude Opus 5 roughly nine points ahead there too ^[5][6]. In other words, Meta picked its own scoreboard and still ended up publishing evidence that its flagship rival is ahead on every metric it chose to show.

Meta's launch also invites comparison to DeepSeek's V4 Flash 0731, a similarly low-cost model, and here Muse Spark 1.2 comes out narrowly ahead: Artificial Analysis's Intelligence Index scores it 54 versus DeepSeek's 50, and its GDPval-AA v2 Elo rating of 1631 tops DeepSeek's 1559 ^[7][8]. On the specific benchmarks Meta highlighted at launch, its self-reported 82.9% on Terminal-Bench 2.1 and 59.3% on DeepSWE 1.1 both edge out the figures DeepSeek published for V4 Flash 0731 on its own engineering blog: 82.7% and 54.4% respectively ^[9].

Those numbers deserve a caveat: they come from separate measurement setups rather than one unified table. The Intelligence Index and Elo figures are Artificial Analysis's own independent evaluations, while the Terminal-Bench and DeepSWE numbers pair Meta's self-reported chart against DeepSeek's self-reported figures. Artificial Analysis's own narrative writeup on Muse Spark 1.2 separately lists a lower, independently run Terminal-Bench v2.1 score of 80% for the model, distinct from the 82.9% Meta reported itself ^[8]. Put together, the DeepSeek comparison is real but curated: Meta highlighted the one head-to-head where it wins narrowly, while its own chart elsewhere shows it trailing Claude Code on every metric that matters most.

Independent analysts are skeptical that Meta's approach of co-training the model and the agent harness together gives it a durable advantage. Omdia chief analyst Lian Jye Su noted that rivals are already doing similar integration work, observing that other vendors, such as OpenAI and Anthropic, have been treating harness engineering as part of the training process, and flagged the security and governance requirements enterprises will demand as a likely brake on adoption ^[10].

Pareekh Jain of Pareekh Consulting argued that Muse Code's real test will be enterprise project outcomes and how much human intervention it actually removes, expecting companies to start it on narrowly scoped, lower-risk tasks before trusting it with production code ^[10]. Counterpoint Research's Neil Shah went further, arguing that vendor-published benchmark charts, like the Terminal-Bench and DeepSWE comparisons Meta itself chose to publish, matter less than real-world results, since the key metric for CIOs is the pass rate against an enterprise's own pipeline ^[10].