Muse Code Windows Support: How to Run It in WSL2

Muse Code Windows support resolves in a single sentence: there is no native build. The launcher matches your system against exactly four platform strings — Darwin arm64, Darwin x86_64, Linux arm64 and Linux x86_64 — and exits with an unsupported-platform error on anything outside that set. Windows sits outside it, so no Muse Code Windows download exists.

That makes the usual search results misleading. Muse Code has no .exe, no MSI, no winget package and no Store listing. Anything offering one is not distributing Meta's build; the only documented entry point remains the shell installer on Meta's developer site.

What does work is WSL2. Windows Subsystem for Linux runs a real Linux userland, and Muse Code installs inside it exactly as on a native Linux box. Be precise about the status of that workaround: Meta has not said WSL is supported, tested or recommended. Muse Code runs there because the Linux build runs, not because anyone promised it would.

Everything else is unchanged under WSL. Muse Code still bills per token with no free tier (see Muse Code pricing) and is still terminal-only, covered on what Muse Code is.

1. Enable WSL2

   Open PowerShell as administrator and install the subsystem, then reboot when prompted. Microsoft documents the current command plus prerequisites in its WSL install guide.

   wsl --install

2. Install and open a Linux distribution

   A mainstream glibc distribution is the safe pick, because that is what the Muse Code Linux build targets. First launch asks for a Linux username and password.

   wsl --install -d Ubuntu
   wsl

3. Run Meta's installer inside WSL

   Run Meta's command from inside the Linux shell, never from PowerShell. Muse Code writes its binary to ~/.local/bin/muse in your WSL home directory and appends a PATH line to the Linux profile.

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

4. Complete the browser hand-off

   Muse Code prints an auth.meta.com verification link before trying to open a browser. If nothing opens, paste that URL into a Windows browser and approve there.

   exec $SHELL -l
   muse

5. Verify inside WSL

   Two clean answers mean Muse Code is installed in the Linux userland and ready to work on files there.

   which muse
   muse --version

The OAuth browser hand-off

This step is what actually trips people. Muse Code sign-in runs a device-style OAuth flow against auth.meta.com: it prints a verification link, tries to open your default browser, then polls until you approve. Inside WSL there may be no Linux browser, so the hand-off to a Windows browser is not guaranteed to fire. The fix is manual — paste the printed URL into Edge or Chrome on the Windows side and approve it while the terminal keeps polling.

The /dev/tty requirement

Approval is read from /dev/tty, so Muse Code needs a genuine interactive terminal. A normal WSL shell provides one, which is why this route works at all — but a script, a CI runner or a nested container inside WSL removes that terminal, and sign-in stalls with no useful error. The same root cause explains the Docker failures documented on Muse Code not working.

File paths across the boundary

Keep repositories inside the Linux filesystem. Working from /mnt/c means every file operation crosses the Windows boundary, which is slower and changes how permissions and line endings behave — a poor match for an agent that edits many files per turn. Clone into your WSL home directory and let Muse Code stay on the Linux side.

None of this is unique to Muse Code; it comes with the standard WSL tax on terminal tooling. Knowing it matters, because these symptoms look identical to the ones on the Muse Code install guide.

Competitor prices are as reported in August 2026 — check each vendor's own pricing page before deciding.

Claude Code matches Muse Code most closely in shape: also a terminal agent, but with native Windows builds and a subscription rather than metered tokens. Trade-offs are laid out on Muse Code vs Claude Code.

GitHub Copilot is the cheapest way in and the only one with a meaningful free tier, though its agent sessions consume credits quickly. Side by side: Muse Code vs GitHub Copilot.

Cursor is a different category — an IDE, not a terminal agent — which some Windows developers prefer because nothing crosses a subsystem boundary. See Muse Code vs Cursor, and the ranked field on best AI coding agents.

Meta has made no public statement about a Muse Code Windows build — not a date, not a commitment, not a hint. The launch announcement describes the agent and the model without addressing platform expansion, while that same silence covers two adjacent questions people keep asking.

• An IDE extension. Nothing announced; Muse Code is terminal-only today.
• A desktop or Mac app. Nothing announced.
• WSL as a supported path. Nothing announced. It works, but that is not a promise.

Treat any Muse Code Windows date you see elsewhere as speculation until it appears on Meta's own channels. This page is re-checked against dev.meta.ai during the beta.

• How to Install Muse CodeThe macOS and Linux install path, in full.
• Muse Code Not WorkingSign-in failures, command not found, 401 and 403.
• Muse Code vs GitHub CopilotThe cheapest Windows-native option compared head to head.
• Best AI Coding AgentsThe full ranked field, including everything Windows-native.
• Muse Code AlternativesWhat Windows developers switch to instead of WSL.