🎙️ How I AI: How Meta designed Muse with Alex Cornell
- ID
- 34563
- Status
- summarized
- Published
- 12 Oct 2026, 11:00 PM
- Fetched
- 13 Oct 2026, 12:35 AM
- Provider
- Lenny's Newsletter
- Category
- product-startup
- Original URL
- https://www.lennysnewsletter.com/p/how-i-ai-how-meta-designed-muse-with
- Source URL
- https://www.lennysnewsletter.com/feed
Summary
- Score
- 6.5
- Created
- 13 Oct 2026, 12:35 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
In a Lenny's Newsletter How I AI episode published Oct 12, 2026, Meta design director Alex Cornell describes how Meta designed the Muse AI agent around human conversation rather than software interactions. Key design patterns include progressive disclosure with three transparency levels (emoji, task list, raw logs), a fixed generative-UI structure with dynamic content, and hiding chain-of-thought because Muse is fast enough to operate quietly. Cornell also describes using Muse to turn years of Instagram saves into a shopping catalog, analyze golf and chess games, and transform a 20-year-old blog into a daily podcast.
Why it matters
If you are building an AI agent, this gives concrete UX choices to copy or reject: use tiered transparency so casual users see an emoji while engineers can inspect raw logs, and do not display reasoning just to mask latency if your agent can respond quickly. It also points to Instagram saves as an overlooked personal-data source for consumer agent use cases, which founders can test without building new data capture. No Malaysia or Southeast Asia-specific funding, policy, cloud, telco, payments, or government angle is present in the text.
Discussion angle
Should AI agents show chain-of-thought, or is it mostly latency theater? How would you implement Muse's emoji/task-list/raw-log progressive disclosure for your own users?