Muse Spark 1.3 max is now available, Meta says
Meta now lists Muse Spark 1.3 with max reasoning as available through Muse Code and the Meta Model API. Its updated announcement, checked on September 19, changes the availability picture behind this article's original headline. The announcement is dated September 2 but does not identify when the max configuration became available. Early coverage distinguished limited-preview benchmark results from the configuration broadly available at launch.
Access is only the first comparison
Meta says the model handles longer tasks, asks for clarification and confirms before consequential actions. It also reports roughly 20% fewer tool calls and 25% fewer tokens in its engineers' coding comparisons with Muse Spark 1.2. Those are vendor-reported results, not a measurement of every team's workload.
Availability lets a team evaluate the configuration it intends to deploy instead of extrapolating from another reasoning setting. A useful comparison should hold the task, repository snapshot, tools and acceptance criteria constant. Otherwise, a better result might reflect a different environment rather than the selected model. Keep unsuccessful runs in the comparison: dropping them makes both completion rates and costs look better than they are.
Measure completed work
For a coding trial, record whether each change passes the project's checks, how much human correction it needs, and whether it respects the requested scope. Token use can help explain cost, but fewer tokens do not by themselves establish a better outcome. A short failed attempt can still require an expensive retry.
Tests of autonomous behavior should also include a task that requires clarification and an action that requires approval. Check what the model actually does in the chosen harness before relying on the vendor's behavioral claims. The practical decision is whether a particular configuration completes the team's work reliably enough at an acceptable cost, with the required controls in place.
Correction, September 19, 2026: This article was updated against the current announcement, and unrelated article links were removed.