Meta Adds Max Reasoning to Muse Spark 1.3 After a Two-Day Safety Gate

Meta said maximum reasoning for Muse Spark 1.3 would follow additional safety testing. Two days later, the company released the Max setting in Muse Code and the Meta Model API, giving developers access to the configuration used for many of its strongest reported results.

The change completes a staged rollout: Meta introduced Muse Spark 1.3 on September 2 with other reasoning modes available first, while Max remained behind a safety gate. The setting now brings the highest reasoning level to the coding tool and API used by developers.

The agent-work pitch

Meta positions the model for long-running coding and agent work rather than isolated prompts. It says Muse Spark 1.3 can manage several workflows in one thread, use tools to assemble context from conflicting sources, repair gaps in a plan, and retain information for a final deliverable.

Meta says the model is designed to

• Ask clarifying questions when a prompt is ambiguous.
• Seek help from the user when it gets stuck rather than claim an outcome it cannot produce.
• Confirm before consequential actions and adapt to requests for progress updates or silent background work.

What Max does—and does not—show

Meta used Max for many of Muse Spark 1.3’s strongest reported evaluation results. In internal comparisons, the company said Muse Spark 1.3 used about 20% fewer tool calls and 25% fewer tokens than Muse Spark 1.2—figures about the model release, not a complete pricing or latency analysis for Max.

A proprietary developer route

Muse Spark 1.3 remains proprietary. Meta says it plans an open-weights Muse Spark release but has not identified a version or date; the immediate test is whether developers use Max for sustained work in Meta’s coding tool and API rather than only for difficult one-off tasks.