platform updates · September 21, 2026

Meta opens Muse to third-party developers — the agent app-store war starts

Ten days after Meta’s personal AI agent Muse launched to consumers, Mark Zuckerberg announced on X on September 18 that connector development is now open to third-party developers. The deal: developers “bring the API” while Muse supplies the agent, its browser, and the user’s context — users then reach the service just by asking the agent in natural language. Meta said new connectors were already live with the announcement, though Zuckerberg’s post didn’t name them.

That’s a shift in who builds the ecosystem. At launch, Muse’s connectors — Gmail, Google Calendar, Spotify, OpenTable — were built primarily by Meta itself. An open program with a directory listing is the same app-store playbook that made smartphone platforms sticky: any developer can plug their service into the agent, and the directory becomes the moat. The race now is over which services your agent can reach first — and whether Meta’s directory fills faster than rival plugin ecosystems.

Meta’s security pitch for all of this: every Muse runs in its own dedicated virtual machine with its own visible browser, a separate Sentinel system reviews actions before they reach the internet, you choose read or write permissions per connector, and sensitive actions need your approval — with Muse VM data kept out of Meta’s ad systems. One caveat: Meta’s own Help Center says it does not review custom, user-requested connectors, so anything installed outside the official directory doesn’t carry Meta’s stamp.

Why it matters

The personal-agent era’s winner won’t be decided by the model — it’ll be decided by the directory. Whoever has the most services an agent can reach wins, and Meta just invited every developer to build on its side. If you run a service users might ask an agent to touch, the Muse developer path is open now.

Key facts

Announced by Mark Zuckerberg on X on September 18, 2026 — ten days after Muse’s September 8 consumer launch
Developers bring their API; Muse supplies the agent, browser, and user context; users invoke services in natural language
Launch connectors (Gmail, Google Calendar, Spotify, OpenTable) were built mainly by Meta; the program now opens to outside developers with a directory listing
Meta said new connectors were live at announcement, though the post did not name them
Security model: dedicated VM with its own browser per Muse; Sentinel reviews actions before internet access; per-connector read/write permissions; approval required for sensitive actions; Muse VM data kept out of ad systems
Caveat: Meta’s Help Center says it does NOT review custom, user-requested connectors

Sources

Spot an error? We correct quickly and note it. Contact us via the contact page.

← More AI news