Muse Code: What It Is and How It Ships

Last reviewed 19 September 2026. Every claim below is backed by a source in Sources. Where we have no source, the guide says so.

What Muse Code is

Muse Code is Meta's coding tool. It runs Muse Spark 1.3: the model's announcement on 2 September 2026 described it as "now available on Muse Code and Meta Model API".

How it is distributed

As a native muse CLI, installed from an install script at dev.meta.ai/install.sh.

That is worth saying plainly because it breaks the habit most people have. Muse Code is not an npm package and not a public GitHub repository — you cannot npm install it and you cannot read its source, star it or watch its releases. Checking npm or GitHub for "muse code" and finding nothing does not mean you are looking at the wrong name.

The SDK is not the CLI

There is something on npm: @muse-code/sdk, which was at version 1.3.0 on 18 September 2026, with its repository at meta-models/muse-code-sdk.

Keep the two apart. The SDK is a library you build against. The CLI is the tool you install and run. They share a name and, at the time of writing, a version number, but finding the SDK on npm does not mean the CLI is there too.

Tracking releases is genuinely awkward

If you need to know when Muse Code changes, the obvious routes are all closed:

• The changelog at dev.meta.ai/docs/muse-code/changelog carries no dates on its entries, so you cannot tell whether something landed yesterday or three weeks ago, or order two entries against each other.
• There is no RSS or Atom feed for it.
• There is no public repository for the CLI, so no releases page and no tags.

What is left, and what we do:

1. Watch the npm version of @muse-code/sdk. The registry stamps every publish, so it is the only dated signal we have found.
2. Watch the meta-models/muse-code-sdk repository for SDK-side changes.
3. Diff the docs pages themselves. Meta's developer site is publicly crawlable — permissive robots.txt, a substantial sitemap — so re-reading the changelog page and comparing it to the last copy is a legitimate way to notice an undated entry appearing. This is the opposite of the Muse consumer site, where automated collection is prohibited and we never do this.

Muse Code is not Muse connectors

Different products that happen to share a brand:

• Muse Code is a developer tool you install on your own machine.
• A Muse connector is a consumer integration that lets the Muse assistant act inside your product. Submissions go through muse.ai/platform, and we have a first-hand guide to that form.

Using Muse Code has no bearing on whether a connector gets approved, and shipping a connector does not require Muse Code.

What is not published

• Pricing, and whether there is a free tier.
• Which platforms the CLI supports, and its system requirements.
• Whether the CLI and @muse-code/sdk version numbers are meant to track each other, or drifted into matching.
• What the changelog entries actually correspond to in time.
• Whether the CLI source will ever be published.