Begin with the layer that failed
An installation error, an account-access problem, and an interrupted running task need different checks. Preserve the exact message and identify the layer before changing anything.
| Symptom | First checks | Avoid |
|---|---|---|
| Command not found or download fails | Platform, copied Meta URL, network and shell output | Trying a same-name third-party package |
| Authentication or access unavailable | Intended Meta account, current beta surface, region status | Deleting credentials without current instructions |
| Task stops after launch | Process output, repository state, documented resume flow | Assuming installation is broken |
| Unexpected code changes | Diff, approvals, test results, task history | Continuing before review |
Installation checks
- Confirm you are on macOS or Linux, the platforms named by the current Meta command.
- Copy the installer again from Meta’s product page.
- Confirm the host is
dev.meta.ai. - Read the HTTP or shell error. A network block, shell syntax issue, and access denial are not the same failure.
- Do not substitute an unrelated package because it has a similar name.
The installation guide preserves the current command and source boundary.
Access and login checks
Muse Code is beta. Confirm the product surface is available for the intended account and region before treating login failure as local corruption. If the product shows an access message, preserve it for support or a later source check.
Interrupted work
Meta documents a local event log designed to make the runtime restart-safe. Use the product’s current resume experience, then inspect the repository and rerun the last narrow verification. The public overview does not publish a manual replay command or universal log path, so neither appears here.
Read event log and resume for the verified runtime claim. If the issue is actually access eligibility, use beta availability.
Capture a useful problem report
Record the operating system, time, product page or installer source, exact command, exact error, whether authentication completed, and whether a repository changed. Remove secrets before sharing. A precise report is far more actionable than “Muse Code does not work,” and it helps separate a beta regression from a local network or account issue.