GenAIWiki
Developer tool

Muse Code Verified

Muse Code is Meta's beta terminal coding agent powered by Muse Spark 1.2. It plans repository changes, writes code, and validates results, coordinating persistent async background agents rather than spawning a new helper for every step. The runtime appends every model call, tool run, approval, and edit to a local event log so sessions are replay-exact and restart-safe. Bundled skills include /plan for an approval-gated plan, /grill to stress-test that plan, and /goal to work toward a stated objective. Official install is macOS or Linux via Meta's installer.
API not listedBeta; verify current Meta access and Meta Model API pricingcodingagentclimetamusesubagentsterminal
FeaturedUpdated todayLast verified: September 2026

Key insights

Concrete technical or product signals.

  • Muse Code is the official harness Meta co-trained with Muse Spark 1.2, so evaluate the pair together rather than swapping in an unrelated CLI.
  • The replay-exact event log is the operational differentiator for long-running tasks that must resume after a crash.

Use cases

Where this shines in production.

  • Large-repository planning, implementation, and validation in the terminal
  • Long-horizon coding tasks that need restart-safe agent sessions
  • Approval-gated plans with /plan, /grill, and /goal
  • Evaluating Muse Spark 1.2 in its intended coding harness

Limitations & trade-offs

What to watch for.

  • Muse Code is a beta; behavior, install support, and availability can change quickly.
  • The official installer is documented for macOS and Linux; do not assume Windows support from the announcement.
  • A local coding agent still needs secret hygiene, tests, branch protection, and human review of diffs.

Models referenced

Declared model dependencies or integrations.

Muse Spark 1.2

Related prompts

Hand-picked or latest prompt templates.

Looking for a tighter match? Search the prompt library.

Muse Code FAQ

What is Muse Code?

Muse Code is Meta's beta terminal coding agent powered by Muse Spark 1.2. It plans repository changes, writes code, and validates results, coordinating persistent async background agents rather than spawning a new helper for every step. The runtime appends every model call, tool run, approval, and edit to a local even...

When should teams use Muse Code?

Large-repository planning, implementation, and validation in the terminal

What should teams watch out for with Muse Code?

Muse Code is a beta; behavior, install support, and availability can change quickly.

Related

Comparisons, platforms, and models teams often view next.

This page is based on publicly available documentation, benchmarks, and real-world usage patterns. Last reviewed for accuracy recently.