# Facebook M **Aliases:** M, Messenger M **Entity class:** Historical personal AI agent **Developer:** [[wiki/Meta|Facebook / Meta]] **Operational period:** 2015–January 2018 **Maturity:** Historical ## Definition **Facebook M** was a personal assistant tested inside Messenger that accepted open-ended requests and returned completed outcomes such as reservations, purchases, travel arrangements, deliveries, and interactions with service providers. It combined artificial intelligence with human “M trainers,” allowing the interface to promise a wider action surface than the automated systems of the period could perform alone. ## Architecture M's software interpreted requests and attempted the work; human trainers reviewed, completed, or extended tasks that exceeded the automation. Facebook recorded the trainers' steps so their work could become training material for later automation. The system therefore functioned simultaneously as a service, a human–machine execution layer, and a data-generation process. Contemporary reporting cited in [[wired/Wired About Personal Agents Named M|Wired About Personal Agents Named M]] placed the beta at roughly 10,000 Bay Area users and estimated that M never exceeded about 30 percent automation. Those figures describe the reported test, not a public technical audit. Meta's own 2016 description called M a “digital virtual assistant, powered by human-trained AI.” ## Historical Importance M established the product ontology later occupied by [[wiki/Personal AI Agent|personal AI agents]]: express intent conversationally, delegate the procedural middle, and receive a completed result. Its users learned [[wiki/Agent-Management Literacy|agent-management literacy]]—which objectives could be handed over, how much context they required, and how daily work changes when intent can become action through an intermediary. Its failure to scale was equally instructive. Open-ended completion remained labor-intensive, and a free service could not supply human compute to Messenger-scale demand. Later systems changed the supply side through stronger planning models, browser and computer use, persistent runtimes, memory, connected tools, and explicit approval layers. ## M-to-Muse Continuity [[wiki/Meta Muse|Muse]] is not presented here as the same codebase. It is the later implementation of the same product pattern inside Meta: a conversational surface connected to multi-step action, memory, external services, and completion. M used human trainers throughout much of the execution layer; Muse moves the machine deeper into that layer while preserving human approval and, in a reported internal calling test, briefly reintroducing contractors at a stubborn voice boundary. ## Relationships - **developer:** [[wiki/Meta|Meta]]. - **successor product pattern:** [[wiki/Meta Muse|Muse]]. - **system category:** [[wiki/Personal AI Agent|Personal AI Agent]] and [[wiki/Agentic AI|Agentic AI]]. - **human capability:** [[wiki/Agent-Management Literacy|Agent-Management Literacy]] and [[wiki/Asymmetry of Agency|Asymmetry of Agency]]. - **execution boundary:** [[wiki/Human-in-the-Loop|Human-in-the-Loop]]. ## Sources / Provenance - [WIRED — Facebook's Human-Powered Assistant May Just Supercharge AI, August 26, 2015](https://www.wired.com/2015/08/how-facebook-m-works/) - [WIRED — Facebook’s Virtual Assistant M Is Dead, January 8, 2018](https://www.wired.com/story/facebooks-virtual-assistant-m-is-dead-so-are-chatbots/) - [Meta — Here’s to 2016 with Messenger](https://about.fb.com/news/2016/01/heres-to-2016-with-messenger/) - [Meta — M suggestions in Messenger, April 6, 2017](https://about.fb.com/news/2017/04/m-now-offers-suggestions-to-make-your-messenger-experience-more-useful-seamless-and-delightful/) - [[wired/Wired About Personal Agents Named M|Wired About Personal Agents Named M]] **As of:** 2026-09-28