Skip to main content

Meta's Muse Spark 1.2 Landed in OpenCode Go — and Most of the World Can't Touch It Yet

Open Source Factory

Meta's Muse Spark 1.2 Landed in OpenCode Go — and Most of the World Can't Touch It Yet

Cheap, fast, genuinely competitive coding model… then the "not available in your region" wall.
August 19, 2026
metamuse-sparkcodingopencoderegion-lock

Open a fresh OpenCode Go account and scroll the model list and you'll see a name that wasn't there a week ago: Muse Spark 1.2 Contributor, Meta's new coding model, priced at a laughably cheap $0.10/M input / $0.20/M output. Try to fire it up from a country outside Meta's shortlist, though, and you hit a wall with a message that's become famous in dev circles this month:

Model API is not available in your region.

I clicked it. I got the wall. If you're outside the US (and a handful of other countries), you will too. Europe? Blocked. Canada? Blocked. Vietnam, Argentina? Blocked. The model is real, the benchmarks are genuinely good, and the price is aggressive — but none of that matters until Meta's regional gate opens.

Let me unpack the three things that actually matter here: how good the model is, that it's now sitting inside OpenCode Go, and exactly why your country is locked out.

What is Muse Spark, anyway?

Muse Spark is the first model from Meta Superintelligence Labs (MSL) — the new Meta division run by Scale AI founder Alexandr Wang. It's the opening act of Meta's Muse family, and it's a genuinely different animal from the open-weights Llama line: Muse Spark is closed-weights and hosted. You can't download it, you can't run it on your own GPU, you can only reach it through Meta's own API (or partners like OpenRouter and now OpenCode).

What it brings to the table

  • 1M-token context window — the "throw the whole repo at it" flagship feature.
  • Truly multimodal input — text, image, video, audio, PDF. It reasons over screenshots and documents, not just code.
  • Agentic-first design — parallel tool calls, sub-agent delegation, computer and browser use, built to run long multi-file coding tasks.

It's the same engine that already powers Meta AI — which launched in Korea back in May, by the way. The consumer app and the developer API are two very different gates, and that distinction is the whole plot of this post.

Benchmarks: is the hype real?

Short version: yes, it's competitive — and it climbed hard between 1.1 and 1.2. Here's the story in Meta's own official numbers.

Muse Spark 1.1 → 1.2 (Meta's official eval report)

Benchmark1.11.2What it measures
DeepSWE53.3%59.3%Real-world software engineering, long agentic tasks
Terminal-Bench 2.180.0%+6.7 ptsTerminal / CLI agent work
Meta Internal Coding Bench70.6%Meta's own coding eval
AC Bench48.4%54.8%Agentic coding (3rd-party)

On DeepSWE 1.1 — the benchmark devs now watch most closely — Muse Spark 1.2's 59.3% lands it third, right behind Opus 5 (65.0) and GPT-5.6 Terra (64.8).

DeepSWE — Muse Spark vs the frontier (Meta official figures) 020 406080 53.3 Muse 1.1 59.3 Muse 1.2 64.8 GPT-5.6 Terra 65.0 Claude Opus 5
DeepSWE scores from Meta's official Muse Spark 1.2 eval.

And on Meta's own internal coding bench, 1.2's 70.6% actually beats GPT-5.6 Terra (65.4) and Gemini 3.6 Flash (63.9) — while sitting about nine points behind Claude Opus 5 (79.4). That's a remarkably candid admission from Meta: even on a test it designed itself, Anthropic still wins.

Intelligence Index (Artificial Analysis) 1.01.11.2GPT-5.5 43 51 54 55
+11 points since the April 1.0 launch; now effectively tied with GPT-5.5.
GDPval-AA v2 (Elo) Opus 51852 GPT-5.6 Sol1730 Kimi K31685 Muse 1.21631 Muse 1.11371
Muse 1.2 ranks #5 on long-horizon agentic work.

How to read this section: I'm using Meta's vendor-reported figures for the headline tables and flagging where third parties (Artificial Analysis, Vals) verify them. Treat any single-source number as "says Meta."

The price: where it gets interesting

Meta split Muse Spark 1.2 into two tiers by model ID:

TierModel IDInputOutputThe catch
Contributormuse-spark-1.2-contributor$0.10/M$0.20/MMeta keeps your data for training · select countries only
Standardmuse-spark-1.2$1.25/M$4.25/MData not retained for training

The Contributor tier at ~$0.30/M total undercuts almost everything on the board — cheaper than DeepSeek V4 Flash and MiMo-V2.5, and orders of magnitude below Opus or Sol. That price is real, but it's priced that way because you're the product: your code and prompts become Meta's training data. If you're stringing together anything proprietary, that trade is a real cost, not a freebie.

It just landed in OpenCode Go

Here's the part that got me excited before the wall hit back: OpenCode Go — the cheap $5/month-first subscription for open coding models — has added Muse Spark 1.2 Contributor to its lineup. Go's model list now reads:

Grok 4.5 · GLM-5.3 · GPT-5.6 Luna · Kimi K3 · MiMo-V2.5 · MiniMax M3 · Muse Spark 1.2 Contributor · Qwen3.8 Max · DeepSeek V4 Pro & Flash · Hy3 · …

Go is designed specifically "for international users," hosted across the US, EU, and Singapore for stable global access — which is why Korea and most of the world can use it for everything else. It's the confirmation that Meta sees agent-CLI distribution as the beachhead for Muse: an OpenAI-SDK-compatible, "bring your own harness" model baked straight into the tools people already run.

But here's the thing that trips everyone up — and it's the whole point of this post:

OpenCode Go lists the model. OpenCode Go does not unlock it.

Go is a proxy — it resells the route. The actual inference still runs on Meta's own infrastructure behind Meta's own regional gate. If Meta's whitelist excludes your country, OpenCode Go can't do anything about it, because the model never reaches Go's servers — your request dies at Meta's door.

That's why you get "not available in your region" even though you're paying for a plan that lists the model. It's not a billing problem. It's not an OpenCode problem. It's a Meta jurisdiction problem.

Why is your country locked out?

Meta restricts the Muse Spark developer Model API with a three-layer gate, which is why workarounds mostly fail:

LayerWhat it checksCan you beat it?
1 · Geo IPYour IP must resolve to an allowed countryVPN gets past this
2 · Account regionYour Meta dev account's profile region must be allowed (effectively US for much of the rollout)← stops most people
3 · Phone / SMSVerify with a phone number from the allowed region← final wall

A VPN gets you past layer 1, then layers 2 and 3 stop you cold. That's why the community reports are so consistent: EU users get the wall, Canadian users get the wall, and "my country is definitely not sanctioned" users in Vietnam and Argentina get the wall too. It's a region whitelist, not a sanctions filter.

The frustrating irony for Korean readers: Meta AI (the consumer chatbot) has been live in Korea since May 2026 — but that's the hosted app in your browser. The developer Model API is a separate availability decision, and Korea simply isn't in the whitelist yet. Same company, same model, two entirely different doors — one open to you, one locked.

Meta says it's "expanding global access" and that the Contributor tier is "available in select countries." Translated for normal people: they know it's restricted, they're working through a country list, and it's not you yet.

Honest limitations (the part nobody else says)

  • Closed weights. No local install, no self-hosting, no fine-tuning. This is the anti-Llama. Your GPU can't touch it.
  • Region wall is the biggest blocker today, and it's a business/legal decision, not a technical one. Expect slow, uneven rollout.
  • Contributor tier = data mining. Cheap by design. Read the retention terms before feeding it your codebase.
  • Harness-inflated gains. Some of the 1.1→1.2 benchmark jump is the Muse Code agent, not pure model. Meta's own chart labels admit the 1.1 baseline ran in a different harness.
  • Missing numbers. Meta hasn't published full 1.2 eval tables (no SWE-bench Verified at launch); the coding strength is real but partially self-reported.

Bottom line

Muse Spark 1.2 is a legitimately strong model — competitive with the frontier on coding, aggressive on price, and now riding the rails of OpenCode Go, the tool most of the non-US world already uses. That combination is exactly why it matters to people like us who don't live in a whitelisted country.

But right now the gate is closed for most of the planet, and no amount of reseller enthusiasm from OpenCode Go changes the fact that the model physically never leaves Meta's servers. If you're outside the shortlist, the practical move is: keep an eye on the country list, don't build production on a data-collection tier, and by all means route a test through OpenRouter if your region gets the green light — because when the gate opens, this is one of the most cost-competitive coding models on the board.

Open Source Factory · written by a maker, not a marketer
Figures: Meta official eval + Artificial Analysis + Vals. Caveats flagged inline.

Related on this blog: Meta just open-sourced its agent model: Muse Glimmer, a 30B that runs on your machine · Xiaomi AI Cube: 120B Local Models at 4.5× DGX Spark's Bandwidth

Comments