En 30 segundos
Claire Vo tests Muse Wonder on a selection of agent, coding and creative tasks using an LLM judge and her own assessments. Her results are a first look tied to the chosen tasks, setup and subjective criteria.
- 1Company claimsVo summarizes Meta’s claims before testing.
- 2Test setupThe model ran through a specific headless setup.
- 3Judging methodA language-model judge and the reviewer scored selected tasks.
- 4Initial resultsHer small sample favored agentic work over design.
- 5Billing taskA billing scenario included multiple planted complications.
- 6Design issuesSome prototypes had missing details or nonworking elements.
- 7TimingLatency observations need further measurement.
Conclusiones
- Vo summarizes Meta’s claims before testing.
- The model ran through a specific headless setup.
- A language-model judge and the reviewer scored selected tasks.
- Her small sample favored agentic work over design.
- A billing scenario included multiple planted complications.
- Some prototypes had missing details or nonworking elements.
- Latency observations need further measurement.
Lee el texto editado por capítulos
Claims and setup
The model and the reviewer’s method.
In this October 2026 first look, Claire Vo tests Meta’s Muse Wonder model on her own How I AI tasks. Her rankings combine an LLM judge with her personal assessment and should be read as a small, subjective evaluation rather than a universal leaderboard.
Vo summarizes Meta’s claims about agentic work, coding, memory and sustained effort. She treats these as the company’s stated positioning before comparing them with her own observations.
For the test, Vo obtained access to Muse Code and ran it headlessly through another coding agent. She says she did not thoroughly evaluate the Muse Code interface itself, so the results concern this particular setup.
Her benchmark includes nearly 20 tasks across prototypes, coding, writing, agent workflows and creative work. An LLM judge and Vo’s voice-note assessments both contribute to the review; task selection and judging methods can affect the rankings.
Task results
Agentic work, writing and prototypes.
Vo says the model performed well on her agentic tasks and adequately on two coding tasks. She was less satisfied with design and some creative outputs. These are first impressions from a limited set of examples.
One test asks an agent to resolve a complicated billing ticket in an administrative app, including an account mismatch, a duplicate and a prompt-injection challenge. Vo reports that the model handled the planted issues in her run.
She liked the model’s concise emails and conversational assistant tone for her own use. That preference is subjective and does not establish that generated messages are always correct or suitable to send without review.
For product-requirements documents and interface prototypes, Vo found missing detail, nonworking elements and design choices she disliked. She says she would continue testing before drawing broader conclusions about coding.
Creative work and verdict
Illustrations, video and latency.
The SVG illustrations were usable in her view but ranked below several alternatives in her selected comparison. The short-video test found an acceptable passage, while she disliked its visual overlays and audio.
Vo reports quick responses on some one-shot tasks and longer runtimes on agentic work. She speculates that a sustained-effort mode may play a role but says she needs more measurement.
Her tentative conclusion is to try the model in agent workflows while continuing to use other tools for design. The video records one reviewer’s preference at a particular point in time.
Más de este canal
35:10EN
29:40EN
16:22EN
36:33EN
37:47EN
35:41EN