What you are starting with
Muse Code is Meta’s beta terminal coding agent. Meta says it is powered by Muse Spark 1.2 and is designed for complex work across large repositories: planning changes, writing code, and validating the result. Its runtime also includes persistent background agents and a local event history intended to make interrupted work restart-safe.
- Status
- Beta Current Meta label
- Interface
- Terminal Official launch surface
- Model
- Muse Spark 1.2 Co-trained with the agent
- Installer
- macOS + Linux Current published command
A practical first-run sequence
- Confirm the source. Start from Meta’s current Muse Code product or research page, not a same-name package or an old search result.
- Confirm the platform. The current official command is published for macOS or Linux.
- Review rates and data use. Standard and Contributor have different rates and different product-improvement labels.
- Install from the current Meta domain. The exact verified command is maintained in the installation guide.
- Begin with a bounded task. Ask for a change you can inspect and validate rather than handing a beta agent an open-ended production migration.
- Review the result. Treat generated code, tool output, and approvals as work that still needs your engineering judgment.
What the beta currently documents
| Capability | Current evidence | What not to assume |
|---|---|---|
| Repository work | Planning, code changes, and validation | A guarantee that every task completes |
| Background agents | Multiple persistent agents can coordinate | A fixed universal agent count |
| Recovery | Local event history supports restart-safe resume | A specific storage path or retention period |
| Availability | Beta with expanded global access wording | Every country and account is eligible |
Bundled skills named by Meta
Meta’s Aug 5 launch announcement names three default skills. The descriptions below stay within the definitions published there:
| Skill | Current official definition |
|---|---|
| /plan | Turns a task into an approval-gated plan |
| /grill | Stress-tests that plan until it holds up |
| /goal | Works toward successful completion of the specified objective |
These are bundled workflow controls, not separate models or pricing tiers. Re-check the current Muse Code documentation before assuming behavior beyond those published definitions.
Pick the next guide by decision
- If you are ready to install, use the current beta installation guide.
- If cost determines your trial, read Standard and Contributor pricing and then use the cost calculator.
- If source-code policy is the constraint, start with data and privacy questions.
- If access is unclear, check beta availability before troubleshooting the installer.
The useful mental model is simple: access first, policy second, task third, verification throughout. That ordering keeps a cheap token rate or an impressive agent demo from deciding a higher-stakes code-handling question for you.