Muse Code Availability: US, Canada, China, Hong Kong

The short version

Creators in the US, Canada, China, and Hong Kong ask the same question: can I run Muse Code and point it at a screen-demo editor?

Honest answer from Meta's public pages we checked:

• Muse Code installs on macOS and Linux with one shell command (docs).
• Meta describes expanded global access for Muse Spark 1.2 in Muse Code / Model API (AI Developers blog, research note).
• Those pages do not publish a country-by-country eligibility list.
• For US / Canada / China / Hong Kong: verify eligibility on your Meta / dev.meta.ai account during auth. Treat live auth as the source of truth for your account.

Same install path on Mac

Wherever Meta grants your account access, the documented install is the same:

curl -fsSL https://dev.meta.ai/install.sh | sh
muse --version

Then:

cd /path/to/your/project
muse

Authenticate with browser sign-in or an API key (/login to reopen). CI and headless runs use META_API_KEY (auth).

Meta's blog post sometimes shows | bash instead of | sh. Follow the live docs command you trust; it is the same installer host.

What "expanded global access" does and does not mean

Does mean (per Meta wording): Muse Spark 1.2 is positioned with broader developer access in Muse Code and the Model API than older preview messaging.

Does not mean: a public checklist that says "available in China" or "available in Hong Kong" as a settled fact on the pages we checked. Contributor-tier wording about "select countries" also appears in Meta materials without a full published list. Verify on your account instead of assuming a country green light.

If auth fails, keep the error text, check account region/terms in the Meta developer surface, and retry when Meta says your account is eligible.

Soft path if Muse Code auth fails

You can still ship screen demos on ScreenKite today.

ScreenKite featured catalog agents (copy): Claude Code, ChatGPT Codex, Antigravity, Grok Build, Kimi.

Muse Code, when your Meta account allows it, is an extra BYO path via local MCP/CLI. It is not an in-app ScreenKite catalog expansion, and ScreenKite does not ship Muse Code in the product agent picker.

Practical soft path:

1. Install ScreenKite (account required; macOS 15+).
2. Open a .skbundle and use a featured agent you already pay for.
3. When Muse Code auth works later, add mcp_servers in Muse settings pointed at ScreenKite's local loopback MCP (extending). Remember: MCP tools are not sandboxed.

Pricing note

Prefer Meta's live pricing and rate limits and authentication and billing for Muse dollars. ScreenKite's AI fee remains $0; you pay Meta for Muse usage under Meta's plans. There is no ScreenKite subscription: Free to start. Pay once to own.

Facts (checked 2026-09-15)

Also read

• How to edit screen demos with Muse Code and ScreenKite
• Muse AI vs Muse Code vs Muse Spark for creators

Bottom line

Try the documented install. Prove eligibility at login. If Meta blocks your region or account, keep shipping demos in ScreenKite with the featured agents you already use, then add Muse Code as BYO when auth succeeds.

Download ScreenKite. Free to start. Pay once to own.