Products · 9 Jul 2026 · 2 min read

Meta ships Muse Spark 1.1 for agentic coding

Meta's new Muse Spark 1.1 agent targets large-scale code migrations and bug fixes, entering a space currently dominated by OpenAI and Anthropic.

Pen-and-ink illustration: a new, intricate cogwheel being fitted. For the story "Meta ships Muse Spark 1.1 for agentic coding".
— Pen-and-ink illustration: a new, intricate cogwheel being fitted. For the story "Meta ships Muse Spark 1.1 for agentic coding". —

What happened

Meta launched Muse Spark 1.1 on Thursday, a new multimodal AI model built for agentic coding. According to TechCrunch, the model is designed for complex processes like multistep reasoning, managing workflows, and deploying features in enterprise systems. Meta is pricing it at $1.25 per million input tokens and $4.25 per million output tokens. The company is pitching it for large agentic workloads, fixing bugs, and helping with major code migrations.

How the room's reading it

The consensus is that Meta is playing catch-up. OpenAI and Anthropic have offered similar models for some time, so Spark 1.1 enters a crowded market. The main angle watchers have spotted is price — it's competitive, though slightly above some rivals like Anthropic's Claude Haiku 4.5. Mark Zuckerberg's rare post on X framed it as a 'strong agentic and coding model at a very low price', signalling Meta's intent to compete aggressively. Developers on X are noting that while the pricing is sharp, the real test will be its performance on the complex, agentic tasks Meta is promising.

Sailfish's take

We're always interested in new tools for automation, but we're cautious about 'agentic' claims for big jobs like code migration. We've shipped enough complex systems to know these migrations fail in subtle, expensive ways. The real cost of an agent isn't the token price — it's the engineering time spent debugging its failures. Meta's pricing is attractive, but it doesn't change the underlying difficulty. We'd start by using Spark 1.1 for smaller, well-defined tasks like fixing specific bugs or automating simple workflows. We'll wait for independent benchmarks before trusting it with a full codebase migration.

Our take — your read?

Be the first to weigh in.

Sources
— END OF DISPATCH — Products