0
MODEL SIGNAL · META · NEW

Muse Spark 1.2

Muse Spark 1.2 is a natively multimodal reasoning model from Meta optimized for complex agentic tasks and coding workflows.

CATEGORYMultimodal
CONTEXT1M tokens
RELEASEDAugust 5, 2026
Key Features
  • Multimodal input with text and image (no primary-source evidence of video, audio, or PDF support for 1.2)
  • 1 million token context window
  • Optimized for complex agentic and coding workflows; used to power the Muse Code terminal coding agent

Provider announcement →

Read the Model Signal report →

MODEL SIGNAL

Meta Muse Spark 1.2

A natively multimodal reasoning model engineered for long-context agentic coding workflows.

Bottom line

Meta has introduced Muse Spark 1.2, a natively multimodal reasoning model designed specifically to handle complex agentic tasks. Armed with a 1 million token context window and text-and-image inputs, the model is built to drive software engineering workflows and actively powers Meta's Muse Code terminal coding agent.

Signal

The clearest signal is Meta's targeted focus on deep-context developer tooling. By anchoring Muse Spark 1.2 to the Muse Code terminal agent, Meta is moving beyond generic chat use cases and directly into autonomous, codebase-level reasoning. The confirmed 1M-token context window allows operators to inject entire repositories, extensive API documentation, or extensive logging traces into a single prompt. Furthermore, the verified text and image multimodal support indicates that the model can interpret architecture diagrams or UI mocks alongside source code—a critical capability for end-to-end engineering tasks.

Noise

There is notable noise surrounding the model's supported modalities and its exact deployment timeline. While moving telemetry from third-party routing catalogs claims Muse Spark 1.2 supports video, audio, and PDF document ingestion, primary Meta sources currently only evidence text and image inputs. Operators should treat these expanded modality claims as unverified. Additionally, a definitive general availability timeline remains unresolved in primary documentation; operators should treat release dates circulating in telemetry metadata as unconfirmed until Meta solidifies its deployment posture.

Where it fits

Directionally, Muse Spark 1.2 belongs in the orchestration and execution layers of software development pipelines. The operator implication is that this model is positioned for heavy-duty, task-oriented agentic loops rather than lightweight conversational routing. Teams building AI-assisted terminal environments, automated pull-request reviewers, or visual-to-code translation tools are the primary audience for this architecture.

Model Signal · Signal + Noise · Isaiah Steinfeld