Muse Spark 1.2 was introduced by Meta AI Research as the model behind Muse Code, a beta terminal coding agent aimed at complex software engineering tasks across large repositories. Rather than spawning helpers per task, the Muse Code runtime pairs a simple main agent loop with a set of persistent async background subagents that stay active throughout the work, planning changes, writing code, and validating results while carrying state forward between steps. A local event log records every model call, tool run, approval, and edit, which makes the runtime replay-exact and restart-safe after a crash so long-running jobs can resume precisely where they stopped. This combination of a long-lived subagent fabric and an append-only execution log positions the model as an agentic coding baseline rather than a single-turn chat model.
In Meta's own engineer comparisons, the follow-on Muse Spark 1.3 used roughly twenty percent fewer tool calls and twenty-five percent fewer tokens than 1.2 to complete the same workflows, signaling that 1.2 set the efficiency bar for this family even though it has since been superseded for frontier work. The model family has been characterized as Meta's flagship line for agentic workflows and coding, with practical fit in repository-scale automation, multi-step refactors, and any task where coordinating several persistent helpers matters more than raw single-prompt quality. Readers looking for an enterprise-grade terminal tool with subagent orchestration and crash-resilient execution will recognize Muse Code as the primary surface, while Muse Spark 1.2 itself sits underneath as the model serving that experience.