How to Install Muse Code on macOS and Linux

1. Confirm your platform

   Run uname -sm and match the result against the four targets Muse Code ships for; anything else stops the launcher.

   uname -sm

2. Run Meta's install command

   Pipe Meta's installer to bash. It resolves your platform, writes ~/.local/bin/muse and appends a PATH line to your shell profile.

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

3. Reload the shell, then sign in

   Open a new terminal so the PATH edit applies, then launch it. Muse Code prints a verification link, opens your browser and polls for approval.

   exec $SHELL -l
   muse

4. Verify the binary

   Two clean answers confirm Muse Code is on PATH and authenticated.

   which muse
   muse --version

5. Run a first task

   Start Muse Code inside a repository and type /plan. You get an approval-gated plan to review instead of immediate file edits.

   cd ~/code/my-project
   muse

Before you install Muse Code, check your platform. The launcher hard-codes four strings — Darwin arm64, Darwin x86_64, Linux arm64, Linux x86_64 — and exits with an unsupported-platform error on anything else. That is the entire Muse Code compatibility matrix.

• Muse Code on Mac: Apple silicon or Intel — you can install Muse Code on either.
• Muse Code on Linux: arm64 or x86_64, mainstream glibc distribution.
• Windows: no native build. WSL2 runs the Linux binary, covered on Muse Code on Windows.
• Network: both dev.meta.ai and lookaside.facebook.com reachable.
• Account: a Meta account with a card on file — there is no free quota, so read Muse Code pricing first.

One requirement is easy to miss: sign-in needs a real interactive terminal, because approval is read from /dev/tty. For what Muse Code does once running, see what Muse Code is and Muse Spark 1.2.

Most people install Muse Code with the one-liner published on dev.meta.ai. Take it from Meta's page, not from any guide:

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

-f fails on an HTTP error rather than saving an error page, -sS hides the progress bar but keeps errors visible, and -L follows redirects.

What the Muse Code script does

It maps your OS and architecture to a supported target, then asks the muse-stable release channel which build to fetch. The Muse Code binary comes from lookaside.facebook.com with a short-lived bearer token, so a proxy blocking Meta-owned hosts breaks the download.

Integrity checking is conditional: when the response carries an x-content-sha256 header, the installer verifies SHA-256 and aborts on a mismatch. Muse Code is then written to ~/.local/bin and marked executable.

Read from the published Muse Code install script and launcher on 6 August 2026; re-check dev.meta.ai before automating against them.

Sign-in happens the first time you run the binary, not when you install Muse Code, and there is no API key to paste. Muse Code starts a device-style OAuth flow against auth.meta.com, prints a verification link, opens your browser and polls until you approve — reading that approval from /dev/tty.

That detail explains launch week's loudest complaint, reported publicly by the Cline team: Muse Code sign-in fails inside Docker, which has neither a controlling terminal nor a browser. Workarounds are on Muse Code not working.

• Identity. A Login with Email option exists on dev.meta.ai, so a Facebook profile is not required.
• Verification. Users report a selfie step at signup; several said on the Hacker News thread they quit there.
• Billing. A card must be on file; Muse Code rates are on Meta's pricing and rate limits page.
• Region. The cheaper Contributor tier is limited to some countries.

Searches for muse spark login and how to access muse spark land here because agent and model share one account: terminal use goes through Muse Code, raw model access through the Muse Spark API.

which muse
ls -l ~/.local/bin/muse
muse --version

People who install Muse Code hit one of two walls. If ls finds the file but which does not, only PATH is wrong — reload the shell rather than reinstalling. If the command resolves but Muse Code will not start, it is authentication: 401 means the stored token expired, while 403 returns the string muse is available to Meta employees, an internal-build gate still in the launcher.

Right after you install Muse Code, open a repository you do not mind the agent touching. Three skills Meta named at launch do the steering — the shortest useful Muse Code tutorial for day one.

• /plan — drafts a plan and waits for approval before executing. Use it by default.
• /grill — stress-tests a plan by attacking its assumptions before code is written.
• /goal — pushes toward an objective across many turns, using the persistent background agents that keep session context alive.

Muse Code writes a local append-only event log, so sessions are replayable and restart-safe after a crash; Meta describes the loop in its launch post. Model specifics are on the Muse Spark model page, the skill surface on Muse Code skills and plugins. Keep session one small: billing is per token, with no hard cap.

rm ~/.local/bin/muse

Muse Code has no separate uninstaller, because the install is one executable. Then open ~/.zshrc or ~/.bashrc and remove the PATH line; if you set MUSE_INSTALL_DIR, delete the binary from there instead. You can install Muse Code again by re-running the command, and deleting it does not cancel billing already incurred. Leaving for good? Muse Code alternatives lists where people go.

• muse: command not foundPATH not reloaded, or never added.
• Sign-in fails inside DockerOAuth needs /dev/tty and a browser; containers have neither.
• 403 and 401 errorsAn employee-only gate string, and an expired token.
• Browser never opens under WSLWSL2 hands the link to Windows; that hand-off breaks.
• Payment method requiredNo free tier; an unbilled account cannot run tasks.