← All posts

Industry

Meta Muse Code: the terminal agent that fans out by default

Meta shipped its first terminal coding agent on August 5, 2026, and its own launch chart shows it losing to Claude Code on every benchmark it published. Muse Code, in beta for macOS and Linux from Meta Superintelligence Labs, runs on Muse Spark 1.2 — a model co-trained with the agent itself. The pitch is not "best model"; it is a design and a price. The design: an orchestrator whose background agents stay alive for the whole session and maintain a shared context file, while implementation fans out to sub-agents in isolated git worktrees. The price: $1.25 per million input tokens and $4.25 output — or 12.5–21x cheaper if you let Meta train on your code.

What shipped on August 5

Meta's launch post describes "a terminal coding agent powered by Muse Spark 1.2" that "takes on complex software engineering tasks across large repositories: planning changes, writing code, and validating the results." It is a single statically linked binary called muse, no app, no IDE extension — 9to5Mac notes that unlike Codex and Claude Code there is currently no dedicated app interface at all.

Muse Spark 1.2 is proprietary and cloud-hosted. Asked about open-sourcing it — the question Meta's Llama history invites — Zuckerberg has said only "I'll have more to share on that soon," per The Register. Codersera's guide reports a follow-up announcement that the weights will eventually open, but nothing has shipped.

The orchestrator design: persistent agents and a shared context file

This is the genuinely different part. Meta describes Muse Code as "a simple agent loop plus a set of async background agents" — and the background agents persist. They "remain active throughout each session, rather than being spawned for individual tasks," which per Zuckerberg avoids redundant information gathering on long multi-step tasks. The Register's summary of the mechanism: when you start a task, background agents maintain a context file that the sub-agents doing the work consult if they lose their way.

Codersera's teardown names four background observers — memory recall, skill recall, and goal tracking on by default, a verification observer off by default — each making its own model calls, so they add token spend. Implementation fans out too: the lead agent spawns write-capable children, and "each child gets its own git worktree, so parallel children never collide." Worktrees are created under .muse/worktrees/ in detached-HEAD state from the lead's commit; your working copy is never touched, and the lead reviews and merges afterward. Concurrency is roughly core count minus two, clamped between 2 and 16, and children cannot spawn children. Zuckerberg's demo claim: "we had it build six features for a game simultaneously with no collisions."

How does that compare to Claude Code subagents? Honestly: it is the same idea with the persistence dial turned up. A Claude Code subagent is spawned per task with a fresh, isolated context window, does one job, and reports a single result back — clean, but each spawn re-gathers context. Muse Code keeps its helpers alive across the session and gives them a shared file to coordinate through, and worktree isolation — an option in Claude Code — is the default for every write-capable child. What Muse Code does not have is Claude Code's ecosystem around the pattern: custom subagent definitions, per-subagent models and permissions, two years of tooling. If you already run multiple agents at once or a full multi-agent setup, Muse Code's contribution is that the fan-out is built in rather than something you assemble.

The other durable idea is the event log: a local append-only record of every model call, tool run, approval, and edit — plain JSONL under ~/.local/share/muse/sessions/ — which Meta says makes runs "replay-exact and restart-safe." muse resume rebuilds an interrupted session from it. Meta's own long-horizon demo leaned on this: a GPU-kernel optimization run of 1,000+ tool calls over 24 hours on NVIDIA Hopper hardware.

Install and first run

The docs version of the installer (Meta's blog and most press print | bash; the docs page prints | sh — same script, same domain):

curl -fsSL https://dev.meta.ai/install.sh | sh
muse --version
muse

The binary is statically linked — no Node, Python, or Homebrew dependency — and lands as a self-updating launcher at ~/.local/bin/muse. First run prompts a browser sign-in with a Meta credential, or you export META_API_KEY for headless use; either way you must add a payment method on the billing page before it executes anything, even on the contributor tier. Then, in a repo:

muse init
muse exec "run the test suite and fix the first failure"
muse skills import --from claude

muse init seeds AGENTS.md for project instructions — and reads CLAUDE.md as a fallback, a frank admission of who got there first. The skills importer pulls from .claude/skills and .codex/skills, and MCP servers configure in ~/.config/muse/settings.json over stdio or streamable HTTP. Bundled skills cover approval-gated planning (/plan), stress-testing a change (/grill), and running to an objective (/goal). The sandbox is on from the first run — Seatbelt on macOS, bubblewrap on Linux, workspace and temp writable, everything else read-only — and it fails closed: if the boundary cannot be enforced, Muse Code refuses to run. The default approval mode blocks rm -rf and sudo; muse --yolo disables prompts, which Meta itself scopes to disposable CI containers.

Pricing: the discount is your data

There is no subscription and no free tier — pay-per-token only, "no minimums or upfront commitment." Two tiers of the same model, from Meta's pricing docs:

• Standard (muse-spark-1.2): $1.25 / 1M input, $4.25 / 1M output, $0.15 / 1M cached input. 3,000 requests and 4M tokens per minute per team. No training on your data; zero-data-retention available through sales.
• Contributor (muse-spark-1.2-contributor): $0.10 / 1M input, $0.20 / 1M output, $0.002 / 1M cached input — in exchange for explicit permission for Meta to train on your prompts and completions. Capped at 100 requests and 3M tokens per minute.

Read both halves of the contributor line. The 12.5–21x discount is paid for with training rights over your code — The New Stack's framing: teams on proprietary code will balk, and for them the cheap tier is not really cheap at all. Codersera's guide adds the operational warning: once code is in the weights, no deletion request unwinds it, so block the tier at the policy layer rather than trusting a config string. And the 30x request-rate cut lands exactly on Muse Code's headline feature — parallel sub-agents burn requests, so the tier priced for experimentation throttles the thing you would experiment with. Web-search grounding bills separately at $2.50 per 1,000 queries.

The benchmarks Meta published show it losing

All figures below are Meta's own launch numbers — vendor-reported, harness included:

Publishing a chart your competitor tops is unusual, and the honesty played better than the numbers. But note what The Register noted: the scores are tightly clustered, the chart is vague about harness details, and a commenter asked why the midline GPT-5.6 Terra appears instead of the top-tier Sol. Generation-over-generation the story is stronger — up 6.7 points on Terminal-Bench and 6.3 on DeepSWE versus Muse Spark 1.1. Early independent runs, per codersera's roundup, put Muse Spark 1.2 fifth on the Vals Index at 71.88% with the lowest cost per test in the top five, and 57.6% on LiveBench agentic coding — its weakest column. Early beta reports match beta status: a Docker sign-in failure, a startup crash, inflated billing figures, and one tester watching the agent spend three minutes researching a Google project that does not exist, then build its plan on the fabrication.

Muse Code vs Claude Code vs Codex CLI

The fuller matchups live in Claude Code vs Codex and the best coding agent roundup; here is where Muse Code slots in:

Frequently asked questions

Where Backgrind fits

Muse Code is exactly the shape of tool Backgrind wraps: another terminal CLI. Backgrind is a desktop overlay that PTY-wraps whatever agent you already run — Claude Code (setup guide), Codex, Cursor, OpenCode, and now muse — and floats it above your other windows, including games in borderless fullscreen.

The multi-agent design makes the pairing more relevant, not less. An orchestrator that fans six sub-agents into worktrees and runs 1,000-tool-call sessions is built for longer unattended stretches — which means more time when the only thing you need from the terminal is a ping the moment it wants an approval or finishes. That is what Backgrind's ambient notifications are: the agent grinds, you get pinged on decisions, and you answer from a toast, a hotkey, or your phone without alt-tabbing into a wall of scrollback.

Sources

Launch post, architecture, event log and the kernel-optimization demo: Meta AI Research. Install command, auth flow, billing prerequisites, pricing and rate limits: Meta's docs at dev.meta.ai/docs/muse-code, auth and pricing-rate-limits, plus the Meta developer blog. Launch coverage and Zuckerberg quotes: TechCrunch and VentureBeat (benchmark figures as published by Meta — vendor-reported). Context-file mechanism, benchmark skepticism and the open-sourcing question: The Register. Training details and evaluation setup: MarkTechPost. Hands-on details — worktree paths, background observers, sandbox, config, gotchas, early bugs and independent leaderboard placements: codersera's Muse Code guide. macOS angle and the no-app note: 9to5Mac. Contributor-tier data trade reaction: The New Stack.