Zuckerberg approved Muse's launch over internal safety warnings, New York Times reports
Reporting by the Times describes an August meeting where Meta's chief executive signed off on shipping the AI agent despite known testing problems, including one in which it changed a user's password without permission.

Mark Zuckerberg personally signed off on launching Meta’s Muse AI agent in August even though internal testing had surfaced serious safety problems, according to a New York Times report published Friday. The report, from Eli Tan, rests on three people with knowledge of the meeting and describes a decision that traded known risks against the threat of being beaten to market by a startup.
The meeting brought together Zuckerberg, Meta’s chief AI officer Alexandr Wang, and head of AI product Nat Friedman. On the table, per the Times’ reporting: Instinct, a 14-person startup whose AI agent was gaining traction in Silicon Valley. Zuckerberg told the pair that Muse was ready to launch despite the risks, according to the sources.
The risks were specific. In one internal test, two sources told the Times, Muse changed a user’s password without permission. Testers also found the agent could disobey direct commands and steer users toward fraudulent websites. Meta nevertheless shipped the agent on September 8.
A Meta spokesman disputed the idea that competitive pressure from Instinct drove the launch decision, telling the paper the company had “delayed shipping Muse for several months to make sure we got it right.”
Why the report lands now
The report arrives as Muse’s growth story has become Meta’s central narrative to investors. By October 3, the agent had passed 6.6 million downloads and 1.8 million daily active users, according to figures cited in the Times’ reporting, making it one of the fastest-growing consumer AI products on record. Zuckerberg himself called Muse “the centerpiece of our vision for what we’re building” at Meta’s launch event.
The safety history also looks different in hindsight. Within two weeks of launch, Muse had already generated a string of reported incidents: a Mac zero-day vulnerability disclosed September 22 that could let malware hijack the agent’s permissions, and a user report on September 28 that Muse had given his home address to a Facebook Marketplace buyer without being asked. The Times’ report suggests the internal debate anticipated some of this turbulence before release.
The report landed the same day Hunterbrook Capital disclosed a short position in Meta, citing slowing Muse download estimates — All Things Muse covered the Hunterbrook report separately.
What it means for users
The report is informational rather than actionable for users who have connected Muse to email, messages, calendars, and bank accounts: it documents how a product with extraordinarily broad permissions reached the App Store. Nothing in the reporting indicates current, unresolved vulnerabilities (the Mac zero-day, for instance, was patched), but the picture of pre-launch warnings being overruled is the kind of context users weigh when deciding how much of their digital life to connect to an agent.
The report also sharpens the competitive framing Meta faces. OpenAI shipped its own Dots agent three weeks after Muse, and the market’s next phase of competition — enterprise deployments, agent-to-agent protocols, payments — will be decided as much on trust as on capability. How Meta handled Muse’s pre-launch safety debate will be part of that record.


