Why Is Meta Swimming in a Red Ocean with Muse?

Meta announced Muse Code this week — a terminal coding agent, paired with a new model called Muse Spark 1.2, built to go toe-to-toe with Claude Code and Codex. My first reaction was recognition: another coding harness, another proprietary model, another entrant in a category that already has three well-funded incumbents. My second reaction, a few days and a lot of research later, is that Meta just made one of the stranger strategic bets I’ve seen in this industry.

Here’s the short version. Meta spent over a decade building the most credible argument in tech that a company doesn’t need to own the whole AI stack to win it — PyTorch, FAISS, Llama, a billion-plus downloads. Then, right as the market it was best positioned to dominate finally arrived, it turned around and built a paid, closed, second-place coding agent instead. I want to walk through how Meta got here, why the market it’s now competing in looks like a red ocean from every angle, and where I think this actually goes.

Meta’s Long Run as an Open-Source Shop

Before Llama, before any of the “did Meta abandon open source” headlines, Meta was already one of the most substantial open-source contributors in AI infrastructure.

The model-weight story is where the “Meta open-sources everything” narrative gets messier than it looks. Llama’s original February 2023 weights weren’t deliberately released to the public — they were intended for academic researchers and only became a mass phenomenon because they leaked onto 4chan within days. And the tool that actually made those leaked weights usable on consumer hardware, llama.cpp, isn’t a Meta project at all. It was built independently by a Bulgarian engineer, Georgi Gerganov, specifically because Meta’s own implementation depended on PyTorch and CUDA infrastructure most individual developers couldn’t run. The entire GGUF/quantization stack that underpins the current wave of local-LLM tooling exists because Meta’s own tooling locked most people out, not because Meta built the on-ramp — it’s the same stack I leaned on when I put a homelab RTX 5090 to work running local models earlier this year, care of Gerganov’s project rather than Meta’s.

Even where Meta genuinely leaned into open weights, the license carries an asterisk worth remembering for later: the Llama Community License adds a separate license requirement above 700 million monthly active users, bans training competing models on it, and currently can’t be used or distributed by EU-domiciled organizations at all. “Open weight” was never quite “open source,” and the fine print already excluded a chunk of the sovereignty-minded buyers who’d want it most.

The Pivot: Scale, Wang, and Muse

Wang’s own playbook here reads as closer to Anthropic’s than OpenAI’s: closed weights, enterprise distribution, a “serious partner” brand rather than a consumer-hype brand. Muse Code’s “contributor tier” makes the strategy explicit — it discounts token pricing by roughly 12 to 21 times in exchange for the right to train future Meta models on your code. Given that Meta’s headline AI hire runs what is fundamentally a training-data supply company, that’s not a generosity play. It’s a data-acquisition price, and it’s exactly the kind of trade I’ve flagged as a governance blind spot for any enterprise pointing a coding agent at code it doesn’t want showing up in someone else’s training run.

Meta hasn’t officially killed Llama — older models are still nominally available — but the frontier work has clearly moved elsewhere, and Muse Spark 1.2 lands second on every benchmark Meta itself chose to publish at launch, behind Claude Opus 5, using Meta’s own harness.

Why This Caps Out in the Single Digits

Split the buyer market three ways. Small-to-medium businesses mostly want AI bundled with what they already pay for — Copilot riding along with Microsoft, Codex riding along with an OpenAI subscription. Large, regulated enterprises and governments are increasingly pulled toward sovereign AI: on-prem or private-cloud deployments the enterprise owns outright, for reasons that are as much geopolitical and security-driven as economic. Sovereign cloud infrastructure spend is projected around $80 billion in 2026 alone. That leaves a middle band of mid-to-large enterprises as the only realistic addressable market for a proprietary, pay-per-token coding agent like Muse Code — and Muse Code’s own rate limits (a 60-request-per-minute cap on the discounted tier) suggest Meta is really building for solo developers and small teams, not that middle band at all.

That middle band is also not empty water. It’s the most contested part of the entire industry:

Four incumbents with better distribution, better brand trust, or both, all competing for the exact segment Muse can actually reach.

Meanwhile, the open-weight side of the market — the side actually suited to the sovereign, on-prem tier — has real Western contenders now, and Meta isn’t the strongest one anymore:

None of these match Chinese frontier labs like DeepSeek, Qwen, or Kimi on raw capability yet — I’ve felt that gap firsthand running Qwen as a local daily driver against frontier models, and it’s the actual constraint on the whole “Western sovereign AI” movement — but every one of them is explicitly positioning against exactly the buyer Meta used to own by default.

Nvidia’s Nemotron deserves a specific callout here, because on paper it looks like the strongest counterargument to my whole thesis: Nvidia has more cash than anyone on this list and a long, credible open-source track record. But Nvidia’s actual customers for its highest-margin business are the frontier labs themselves — Meta, OpenAI, Anthropic, xAI all buy Nvidia chips by the gigawatt. Nvidia has no commercial incentive to ship a model that’s genuinely frontier-adjacent enough to threaten the labs writing those checks. What Nemotron actually looks like in practice is closer to an ecosystem-fostering, workhorse model: efficient, well-documented, genuinely open down to the training data, and good enough for agentic “grunt work” tasks — but not positioned, funded, or trained to be the frontier-scale sovereign alternative the market is short on. Nvidia benefits from more AI demand everywhere, on any hardware; it doesn’t benefit from being the company that made its own customers’ proprietary models redundant.

The Blue Ocean Meta Swam Away From

Lay all of that side by side and the decision looks backwards. The sovereign-AI buyer wants Western-provenance, open, auditable, self-hostable models, for reasons that have nothing to do with who has the flashiest benchmark chart. Chinese labs are the strongest open-weight option today, but they’re disqualified for exactly the buyers who care most about sovereignty. That left a wide-open lane for a well-funded, compute-rich, Western lab to become the default frontier-scale open option — and Meta, with more training compute and more open-source institutional muscle than Mistral, Cohere, Poolside, and Arcee combined, was as close to a lock for that lane as anyone in the industry.

Instead, Meta shelved Behemoth, the model that would have been its actual answer to that opportunity, and built a second-place proprietary coding agent that has to fight Anthropic, OpenAI, Google, and now xAI for a market segment that increasingly doesn’t even want a proprietary product. The “why” makes sense as a short-term financial decision — 2026 capex guidance sits at $115-135 billion, and giving that output away for free stopped feeling tenable, especially once Anthropic proved a closed API could scale into tens of billions in revenue. It makes less sense as a long-term strategic one, because it trades a nearly uncontested market for the single most crowded one in the industry, at the exact moment the macro trend was bending toward the thing Meta was uniquely positioned to sell.

Where I Think This Actually Goes

My best guess is that Meta ends up correcting course, but not by reviving Llama as a chatbot competitor. I think Meta goes open-source again on the infrastructure layer, not necessarily the frontier model layer — I’d bet on Muse Code itself eventually becoming an open-source harness, the same way Meta gave the world PyTorch and FAISS instead of hoarding them. Zuckerberg’s own hedge, “I’ll have more to share on that soon” when asked if Muse would open up, reads exactly like a company keeping that door open on purpose.

From there, I expect Meta to chase bottoms-up enterprise adoption through open infrastructure rather than top-down proprietary API sales — get the harness, the tooling, and the developer experience into as many hands as possible, the way Llama’s download numbers built goodwill Muse Code can’t buy at any discount.

But the more specific bet is this: Meta has already proven, at consumer scale, that it can out-execute Microsoft and Google on distribution when it commits to a category — that’s the entire history of Facebook, Instagram, and WhatsApp against every incumbent that came before them. It hasn’t proven that in enterprise yet, and enterprise is the next real growth line available to it. Getting a real foothold there runs through coding first, because coding is where the vibe-coding revolution is already reshaping how knowledge work gets done, and it’s the most measurable, highest-willingness-to-pay wedge into the enterprise stack. If Meta wants a second act, it isn’t “ship a slightly cheaper Claude Code clone.” It’s using distribution the same way it always has, aimed at every knowledge worker inside an enterprise, not just the engineers, priced to make the decision easy at the department-budget level rather than the CTO-approval level.

So the real question isn’t whether Muse Code beats Claude Code on a benchmark chart. It’s whether Meta can do to Microsoft and Google in agentic knowledge work what it already did to them in consumer social media — and whether anyone in Redmond or Mountain View is actually prepared for Meta to try.

By the Numbers

• $115-135 billion — Meta’s 2026 capex guidance, roughly double 2025, the financial pressure behind the closed pivot
• $14.3 billion — Meta’s investment for a 49% stake in Scale AI and Alexandr Wang’s move to lead Meta Superintelligence Labs
• 12-21x — the spread between Muse Code’s standard and “contributor” (data-for-training) pricing
• 2nd place — where Muse Spark 1.2 landed on all three benchmarks Meta itself chose to publish at launch
• 60 requests/minute — the contributor tier’s rate cap, versus 3,000 on standard, a strong hint about who Muse Code is actually built for
• $60 billion — SpaceX’s all-stock acquisition of Cursor, a fourth well-capitalized competitor that landed in the same market the same month
• $47 billion vs. $25 billion — Anthropic’s annualized revenue run-rate versus OpenAI’s, as of April 2026, in the exact enterprise-coding lane Muse is chasing
• ~$80 billion — projected 2026 sovereign cloud infrastructure spend, the market segment open weights are best positioned to serve
• 2.5-3.2% — Meta AI’s approximate global consumer assistant market share, despite sitting on top of Facebook, Instagram, and WhatsApp
• 7 named contenders — the current Western open-weight field (Mistral, Cohere, Nvidia Nemotron, Poolside, Arcee AI, Thinking Machines Lab, IBM Granite) now competing for the sovereign-AI lane Meta once had nearly to itself