On 12 October 2026 Meta released Muse Wonder and Muse Wonder Full, aimed at personal and professional agents rather than a single chat reply. Muse Wonder is on the Meta Model API and in Muse Code. Wonder Full is for Muse Code subscribers. Meta’s write-up is here, and the research note is here.
The names to remember are Active Memory and Active Focus. Memory is how the model keeps what matters across a long task. Focus is how it stays on that task instead of wandering into a plausible side quest. Meta trained both on long-running work: reading a lease, following a claim, building an app, revising code after tests fail.
A long task is a product problem
Most of the model race this month has been about which weights answer a prompt. Wonder is about an agent that is still working after the prompt is gone. That is closer to the software I actually ship. A CRM workflow, a migration, a support case: the value is finishing, not the first paragraph.
Memory is also the risk. A personal agent that can see messages, calendars, and documents will eventually be asked to use one of them. Meta says the family is trained not to share private information without permission, and still to help defensive security work. I would not take that sentence as an access policy. In a product, memory needs a boundary you can read: what was stored, for which task, and who can delete it.
What I would wire up
- A task record the agent writes to, separate from the person’s whole archive.
- A stop when the next action sends data outside that task.
- A person on anything that pays, deletes, or messages someone else.
Wonder Full being subscriber-only is the same split we keep seeing. The name of the family is not the name of the model your app will call. Pin the id.
If you are comparing frontier agents this week, judge them on a task that takes an hour and touches private files. A benchmark score will not tell you whether the memory should have been saved.