返回资讯中心
外部精选
软件工程
#开发者实时流

Alexandr Wang Shipped Meta's Muse in 7 Months

Meta shipped Muse 7 months after its first prototype, with fewer than 200 people and a spreadsheet of 100+ rows deciding when it could launch.

Hacker News 最新swolpers2026/11/10 · 7 天前30 分钟阅读

以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。

Ruben Dominguez

Nov 10, 2026

67

1

1

Share

Meta shipped Muse 7 months after its first prototype, with fewer than 200 people and a spreadsheet of 100+ rows deciding when it could launch.

One of Alexandr Wang’s first acts with OpenClaw was a psychoanalysis prompt Nat Friedman had written, run against Wang’s own email and photos. He calls it “the equivalent of 3 years of therapy compressed into this one moment.” That was February, and 7 months later Meta shipped Muse.

Wang spent 9 years building Scale AI before Mark Zuckerberg called. This interview covers what came next: the prototype, the launch gate, the meme account and the org chart holding it up.

Wang now runs Meta Superintelligence Labs, which he describes as a refounding of Meta’s AI lab, after Meta bought 49% of Scale AI. In his interview with David Senra, he walks through how that lab built Muse, a personal agent aimed at the things people want to do rather than work or coding.

I watched the full interview and pulled out the 10 lessons founders and investors can use this week, plus a launch scorecard template and a Claude prompt to build your own.

Wang’s team built the magic in 1 to 2 weeks. The reliability took the other 7 months.

Taking this prototype where it sometimes worked and was magical, but most of the time didn’t work and would constantly break, and going from there to something that would be highly reliable.

In February, Wang and Friedman each wrote memos that went up to the Meta board, and a prototype followed within 1 to 2 weeks. Much of the final product was already in that first demo, including the Jolly mascot and an early version of the Muse Charm. The launch came 7 months after that.

Writing that kind of memo for your own board? The McKinsey Pyramid Principle wired into Claude structures it the way consultants do, and the board meeting operating system covers what happens after you send it.

OpenClaw shows the other ending. Wang says its wave peaked and faded because people got magic moments while most of the rest broke, and he still calls Peter Steinberger a visionary.

Wang’s description of what Meta added is deliberately dull: “sanding out all of the details” of the model and the product together. Budget the second half before you celebrate the first.

Taking your own agent past the demo? Start here:

3 Founders Shipped Claude Managed Agents to Production in 2 Weeks. Here’s the Playbook

Stop Blaming the Model. Fix the Architecture

The 6 decisions that turn an AI agent into a worker you can leave alone

The AI code review checklist: 8 failure modes and 12 prompts

Every lab sprinted at coding. Wang asked which race Meta already owned.

Meta’s products represent the things that we all want to do.

In February, Anthropic led on coding by a wide margin, and Wang calls it a scary moment. The conventional wisdom said coding agents were the only capability that mattered, so everyone crowded that use case.

Wang had pitched Zuckerberg a different read before the Scale deal happened. People have things they want to do and things they have to do, and AGI shrinks the second pile.

Instagram, WhatsApp and Facebook live on the first one. Wang puts their reach at 3.5 billion a day, while Meta’s Q2 2026 results, released July 29, 2026, count 3.60 billion family daily active people for June, across Facebook, Instagram, Messenger and WhatsApp.

One line in the conversation sums it up: not work, not coding, but personal. Sam Altman’s 900 million weekly users show how big that lane gets, and Meta already owned the distribution to enter it. The Muse operating manual shows what shipped.

Choosing that lane is a product-strategy call before it is a model call. OpenAI’s product lead splits it into four parts in this AI product strategy framework, and 100 AI agent ideas you can build this weekend is a fast way to test which lane your users already live in.

When the whole field crowds 1 race, find the one your users already live in.

Meta’s launch gate was a spreadsheet. A checkpoint with 20 red rows didn’t ship.

We had set, for each of those rows, what threshold is launch blocking and above what threshold is good. We had many checkpoints that were green on 80 of the rows but red on 20 of the rows. We knew that wasn’t good enough.

The sheet began as a list of more than 100 specific behaviors and capabilities the ideal personal agent needed. The team built evals for every row, trained the model against each one, and held reviews on whatever it was still bad at. Wang calls the process “very meticulous.”

Meta’s consumer culture ran on the same habit. Once you know what you’re measuring, talented people optimize it: conversion, referral rates, the onboarding flow.

The first checkpoint to come back green across the board also felt, by hand, far better than anything the team had tried. The number and the feel agreed.

“Decide what red means before you build anything.”

Wang’s sheet gave every row two numbers: a threshold that blocks the launch and a threshold that counts as good. You can start with 10 rows this week. Give each row the behavior, the eval that tests it, both thresholds and today’s score, then rerun the evals on every new model checkpoint.

Here is how the first rows could look for a personal agent, with example thresholds you would tune to your own product:

Finishes a booking end to end: blocks launch below 85% on 200 test requests, good at 95%+

Asks before spending money: blocks launch below 100%, because one surprise purchase ends the trust fall

Remembers a preference from last week: blocks launch below 80%, good at 95%+

Recovers from a failed tool call: blocks launch below 70%, good at 90%+

Checks back when an instruction is ambiguous: blocks launch below 75%, good at 90%+

Then paste this prompt into Claude to draft the full sheet:

You are the head of quality for [PRODUCT], a [ONE-LINE DESCRIPTION] used by [USER]. Draft a launch scorecard of 40 rows. Each row is one behavior a user must be able to rely on.

For every row, give:

  1. The behavior, in one sentence a user would recognize
  2. An automated eval: test inputs, expected result and how to grade it
  3. A launch-blocking threshold and a good threshold, as pass rates
  4. The user moment it protects (first task, payment, memory, error)

Group the rows into core tasks, permissions and money, memory, error recovery, tone and speed. Then mark the 10 rows a new user hits in their first 3 tasks, since those decide retention.

Building your own launch gate? Start here:

Set a metric. Walk away. Let the agent optimize overnight.

Why Most Self-Improving AI Loops Fail and How to Build One That Works

Google Senior AI Leader’s Loop Engineering Masterclass

The Claude Code loops library: 12 ready-to-run recipes

Every executive knew Muse mattered. The discipline was keeping the rest of the company off it.

We knew it was a single work of art. It required strong point of view and strong focus to pull that through into one beautiful experience.

The headcount was under 200, model work and product work together. In big-company terms, Wang says, that is “actually a lot smaller” than it sounds.

The failure he dodged has a name: “PM hell.” Every PM jams a pet feature in, and the product blends into a smoothie that users can feel without being able to explain it.

Steve Jobs comes up too: Apple is Steve Jobs with 10,000 lives. Later, Wang names Friedman as the person whose single point of view came through on Muse.

Small teams keep winning this way, from Luca Ferrari running Evernote with 20 people to OpenAI’s model where 2 engineers beat 200 to the billion-dollar startup formula. Cap the team early and let taste decide what ships.

A feature list can’t be forwarded. A screenshot can.

To have a modern consumer product, it has to work on the screenshot. The screenshot has to fly, either through group chats or word of mouth or online.

Wang says it wasn’t engineered. Putting Jolly in the frame still means any screenshot announces itself as a Muse screenshot. In his words, that is “the best marketing you could possibly have.”

The evidence is a story about a friend running a $100B company. He left his ID on a Flexjet, told Muse he wanted no part in getting it back, and watched it arrange a courier to carry the ID to his office. 3 or 4 screenshots of that exchange did the selling.

The ads gripe is in there too: Anthropic and OpenAI ads sell a logo when millions of use cases could carry the ad. Wang’s team kept asking a simpler question: why would someone care? People care about “what it can do for them,” not about the lab or its research.

Muse ran a few ads, but the early engine was Wang reposting users doing odd things with it. OpenAI’s product lead lays out 15 distribution plays, and speed, story and surface area decide who wins when a product spreads that way.

If your output can’t survive a screenshot, it isn’t ready for distribution.

Growing on a small ad budget? Start here:

Zero Ads. Zero VC. $230M ARR. The Story of Magnific

How Lovable hit $400M ARR in 14 months with 146 people and almost zero paid ads

The Growth Playbook Behind One of AI’s Fastest ARR Climbs

Your GTM run by agents: 8 agents and 3 workflows

The growth accounting and virality model, to measure how far each screenshot travels

Wang knew Meta had distribution. It still needed people to repeat the product in public.

I remembered that the internet rewards risk, and it rewards surprise, and things that people don’t expect.

Wang gives 2 reasons for the posting spree. AI launches arrive as a torrent, so Muse needed a way to break through, and Meta, despite owning Instagram and Facebook, had not been cool for a while.

It began with Wang reposting use cases from users. A few offhand posts did well while he wasn’t looking at his phone, so he leaned in. One, a Jolly holding a briefcase captioned “MFW I go to work on Monday,” told him the mascot had mileage.

He admits meetings got hard to sit through while he drafted the next meme. Friedman’s verdict: he expected to learn about Muse users, and instead “we’re just learning a lot about Alex’s mind.”

There is no tracking, though Wang believes the memes moved growth, and the evidence is anecdotal: the people raising the memes also downloaded the app. For how attention works now, read Social Media Has Changed Forever.

Give your product a character you can drop into any situation.

Friedman went all in on OpenClaw. Most users need a ladder, not a leap.

It’s kind of this trust fall that you have with an AI agent. At first you don’t really trust it, but you’re kind of intrigued, so you give it a little nibble, and then something a little bigger, and something a little bigger, and something a little bigger.

Friedman skipped the ladder. He told OpenClaw he wanted to drink more water, and it watched him on security footage and said good job.

Most people won’t start there. Wang says some college students do: recording voice notes, brain-dumping into the agent and trusting it to turn the pile into plans.

For successful Muse users the climb is bigger and bigger tasks, “and then having it work every one of those times.” A broken rung can end it, and Wang says people left most agent products at the start of the year because they were unreliable.

Muse is also not a chatbot, so non-developers need careful onboarding. Meta’s A/B tests across model versions show the experience tracks model quality closely, including how reliably the agent finishes tasks and checks back when it needs guidance. That sensitivity is model-market fit in miniature.

Design the first 3 tasks a new user hands your agent, because retention is the hardest metric and the AI trust tax is what a broken rung costs.

Wang’s pitch for Muse is bigger than saved time. It is ambition that survives your first job.

I think Muse can give everyone the adulthood they dreamed of in childhood.

Kids think big, he says. By the time they finish school and sit in a job for a while,

正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。

打开原文
去社区讨论 →