Meta announced Muse Wonder on 12 October 2026; the page also shows an update on 13 October. It describes Wonder through the Meta Model API and Muse Code, Wonder Full for Muse Code subscribers, and a later staged rollout to consumer Muse. Those are separate access conditions.
Which layer do you need?
Record the model, the application carrying it and the features available to your own account separately. A team building a prototype should check developer documentation and its account entry. An individual looking for an everyday assistant should check the application they can actually use. Similar branding does not establish identical entitlements.
Our suggested agent evaluation card
- Task: Supply a public product brief and ask for a prototype with a clear account of unfinished work.
- Process: Record missing information, retries and human corrections.
- Result: Check against criteria written beforehand rather than the persuasiveness of a response.
- Boundaries: For real account actions, identify confirmation points, logs and a way to stop.
This is our evaluation method, not a test we have performed on the model. Vendor positioning is not an independent capability ranking, and we have not tested a paid account.
What this means for tool selection
A maintained directory should distinguish an announcement, an available developer entry and access in a particular account. Preserve the input, output and revision history of one small task before expanding a workflow. A single demonstration does not establish reliability on recurring work.
Our related Meta AI profile is an assistant reference, not proof of Muse Code or API entitlements. Regional availability, all plans and current prices were not established in this review.
Source published 12 October 2026, marked updated 13 October; reviewed 20 October. Original Meta announcement. More Global AI Updates.
© Copyright notes
The copyright of the article belongs to the author, please do not reprint without permission.
