A beta terminal workflow for supervised repository tasks
Muse Code is Meta's beta terminal coding agent for supervised, repository-scale engineering work with persistent background agents and an activity record to inspect.
Muse Code is Meta's beta terminal coding agent for longer engineering work in and around a codebase. Meta describes a coding task entering a workflow with persistent background agents; its stated output includes work on that task and a local event log a developer can inspect. It is a tool to assess for supervised repository work, not a replacement for version control, code review, tests, or release controls.
Job
Choose Muse Code when a technical owner wants to explore an agent-led workflow for a bounded, multi-file engineering task and can actively review the result. The product is aimed at longer repository-scale work rather than a quick inline completion. It is most useful when a team can name the task owner, limit the permitted project surface, and decide what evidence is needed before accepting a change.
Input → output
The public product description presents a coding objective in a terminal-based, repository-oriented workflow. Meta says persistent background agents can remain active during the work and describes a local append-only event log for activity such as model calls, tools, approvals, and edits. The intended output is candidate engineering work plus an inspectable record—not an independently verified completed task. Exact task inputs, credential flow, model selection, and behavior on a particular repository remain unknown here.
Workflow shape
- Check the current beta, access, price, and data-use terms for the account and model surface that would actually be used.
- Define a bounded task, the permitted files or environment, and the acceptance checks before invoking an agent workflow.
- Use Meta's current macOS or Linux terminal route only after the local environment and access path are authorized.
- Inspect the proposed work and its activity record, then run the team's normal tests and review before accepting or discarding a change.
This is a human-supervised evaluation loop. A beta agent can help organize and work through a task; the project owner remains responsible for credentials, scope, review, testing, and release decisions.
Choice boundary
Muse Code fits a team that wants to investigate a persistent-agent coding workflow under deliberate supervision. It does not fit a situation that needs a confirmed production-ready installation, settled commercial terms, known data handling, or a proven task outcome before the evaluation begins. Do not use it as the decision maker for security, privacy, compatibility, accessibility, or deployment approval; those need the team's normal evidence and accountable reviewers.
Access and price
The readable official announcement identifies Muse Code as a beta and describes a macOS/Linux terminal installation route. That does not establish a durable access promise. Login, API-key, region, payment, entitlement, second-stage setup, and successful use on a repository were not verified for this tool record.
Current commercial and data-use terms are intentionally recorded as unknown. The official developer product URL supplied with this handoff had previously displayed separate Muse Spark model rows, but it returned an official unavailable-page response when rechecked on 2026-08-08. No current price, billing cadence, currency, token or credit allowance, seat basis, trial, or data-use scope could therefore be reread. In particular, an API model rate must not be treated as the all-in price or data-use policy for a Muse Code beta session without a current first-party page that explicitly connects them.
Verification state
The Meta AI Research announcement was re-read on 2026-08-08. It supports the beta, terminal-agent, persistent-agent, repository-work, activity-record, and macOS/Linux positioning used above. The Meta developer product URL could not be re-read at that time because it returned Meta's unavailable-page response. No installer, sign-in, API key, payment flow, private repository, or production path was used.
The mapped catalog target is /tool-logos/muse-code.webp. No standalone Muse Code mark was located on the readable official pages. The reusable official mark is Meta's primary navigation wordmark SVG, served by Meta's own research site with a 496.2364502 × 100 viewBox and local candidate SHA-256 8940d7ecc943da6891bda1c87e0d479b9d791d78ac479d4210163afaa4ef2391. It is a Meta corporate mark, not a Muse Code product mark, and must not be substituted with an article crop or an unofficial recreation. The fixed media publisher owns conversion and public readback.