Why this site exists
Muse Code launched into a news cycle, and news articles decay long before the questions developers ask do.
Meta Superintelligence Labs released Muse Code in beta on 5 August 2026. Within a day the search results for it were almost entirely press coverage: launch write-ups that repeat the same announcement paragraph and answer none of the practical questions a developer actually has. Where does the binary install? Why does sign-in fail inside a Docker container? What does a real session cost on each tier? Can you cap spending? What exactly does the Contributor tier let Meta do with your code?
This site answers those questions in one place, keeps the answers current while the product is in beta, and cites a source for every claim so you can check the work rather than trust it.
It is written for the developer who is deciding whether to put a coding agent near a real repository — not for someone who wants a product tour.
What this site is not
Being clear about the boundaries is part of being useful, so here is what you will not find here.
This is not a Meta property and has no relationship with Meta. Nothing here is a download mirror: every installation instruction points at Meta's own installer and documentation, and we quote the command rather than host anything.
We do not publish hands-on reviews of software we have not run at length, we do not publish user testimonials we cannot attribute to a real public post, and we do not publish benchmark numbers we generated ourselves. Where a number comes from Meta's own reporting or a third-party evaluation, the page says which, because those two things are not interchangeable.
How this site is funded
There is no paywall, no newsletter upsell, no affiliate arrangement, and nothing to buy here today.
Muse Code Guide currently earns nothing. There are no affiliate links, no sponsored placements and no advertising on the site as of the date at the top of this page. If that changes, this section changes with it, and any commercial relationship that could affect a recommendation will be disclosed on the page where the recommendation appears.
Comparison pages recommend competing products where those products genuinely fit better, including on pages where doing so is inconvenient for the site's own subject matter.
How the work is done
Two further pages set out the sourcing rules and the corrections process in full detail.
- Research methodologywhich sources count as evidence, how claims are graded, and what gets hedged
- Editorial policycorrections, updates, conflicts of interest, and how AI assistance is used
- Disclaimer and trademark noticethe site's relationship to Meta, stated plainly
- Privacy policywhat this site collects when you read it
Contact and corrections
Corrections are welcome and are the fastest way to make this reference more accurate for everyone.
If a figure here is wrong, out of date, or missing the context that would change how you read it, write to hello@muse-code.app. Include the page and, where you can, the source that contradicts it. Corrections are applied at the top of the queue and noted on the page, as described in the editorial policy.
Meta's own announcement, documentation and pricing pages remain the authoritative source for anything about the product; this site links to them throughout rather than asking you to take its word.
Sources
- Meta AI Research — Introducing Muse Code and Muse Spark 1.2research.meta.ai
- Meta developer platform — Muse Spark model documentationdeveloper.meta.com