🎙️ How I AI: Meta Muse Wonder + How Brooke Lacey is scaling video with AI
- ID
- 37008
- Status
- summarized
- Published
- 19 Oct 2026, 11:03 PM
- Fetched
- 19 Oct 2026, 11:36 PM
- Provider
- Lenny's Newsletter
- Category
- product-startup
- Original URL
- https://www.lennysnewsletter.com/p/how-i-ai-meta-muse-wonder-how-brooke
- Source URL
- https://www.lennysnewsletter.com/feed
Summary
- Score
- 7.0
- Created
- 19 Oct 2026, 11:36 PM
- Tags
- Audience
- developersai_agent_usersai_ml_learnersvibe_coderssaas_founders
What happened
In this How I AI episode, Claire runs Meta's new Muse Wonder model through roughly 20 real-world tasks and reports it ranked first on billing-ticket resolution, inbox triage, computer use and email writing at its price tier, with the advantage clearest on long-running agentic tasks where it kept trying different approaches until it hit the goal. She credits an 'active focus' behaviour that spends more time on complex requests, and says it should be kept away from frontend work: on a ChatPRD redesign it ignored brand guidelines, added emojis, broke image rendering, and produced heavy serif fonts, blurple and rounded corners, while prototypes that looked 80% right failed at interaction testing with broken buttons and obstructive overlays. The excerpt does not include detail on the Brooke Lacey video-scaling segment, so that half of the episode can't be summarised from this text.
Why it matters
Use this as a routing decision, not a model swap: the concrete evidence here is a billing-ticket run where Muse corrected an account-linking error, handled duplicate refund logic, changed the customer's plan, drafted a reply, closed the ticket and resisted a planted prompt injection — that is back-office agent work, so trial it there. Budget for latency too, since 'active focus' spends more time on hard tasks than quick ones, which changes the cost/latency maths for anything customer-facing. And treat its prototypes as scaffolding you must finish by hand, not as shippable UI.
Discussion angle
Which of your agent loops would you actually route to Muse Wonder — and does 'active focus' spending more time on complex tasks break your latency or per-ticket cost budget if you put it in front of customers?