Meta launched Muse on September 8 as a personal assistant that follows users across apps, including WhatsApp. Buried in that same build sits a second, unannounced product: a “Shared Agents” tab that opens a working creation flow for building a bot and passing it to other people, according to TestingCatalog. Reporter Alexey Shabanov found the tab live and functional in the current app, even though Meta has said nothing about it in public.

The mechanics point past a personal assistant toward a builder platform. Inside the tab, a user can pick skills for a bot, wire it to outside services, set its appearance and name, and write the instructions that govern how it behaves. Once deployed, the result runs as its own sub-agent thread inside Muse, separate from the user’s main conversation, and can apparently be shared with or accessed by other people.

That is the same basic pitch xAI already makes with Grokbot’s agent builder. Meta’s version could travel further, because it would launch on top of Instagram, WhatsApp, Facebook and Messenger rather than a single standalone chat app. A small business does not need to acquire new customers to reach a Shared Agent; it already has them inside apps they use daily.

The clearest use case TestingCatalog describes is a small business assembling a handful of narrow bots, one for sales, one for scheduling, one for handling customer questions, and then making each available to employees or to the customers themselves. That reframes Muse from a single personal helper into a toolkit a business owner configures once and distributes widely, closer to how a company deploys a shared internal wiki than how it uses a single chatbot seat.

What is missing matters as much as what has surfaced. TestingCatalog says it is still unclear how sharing would be permissioned or distributed: whether a Shared Agent can be published for the public to install, whether Meta charges for it, and who is accountable if a business’s bot gives a customer bad information. None of that has been addressed, and a creation flow that already works in an app build is not the same as a product Meta has committed to ship.

The timing lines up with a real event. Meta’s developer materials for Meta Connect, scheduled for September 23 and 24, already list sessions on “agentic development workflows” alongside Muse Spark and the company’s Business Agent Platform. Meta has not confirmed Shared Agents will appear there, but the agenda makes the date a plausible reveal window rather than a guess. The signal is reinforced by Meta’s recent absorption of the team behind Stilla, a startup that built multiplayer AI agents for teams, which said on social media it is joining Meta to strengthen the company’s business AI products.

Muse Spark and Meta’s model API have already pushed toward tool use and multi-agent orchestration rather than single-turn chat, and a public agent builder would be the logical extension of that direction: instead of one personal Muse, a user or a business ends up managing a small fleet of specialized bots.

For any team currently paying for a third-party agent-builder tool to run customer support or scheduling bots, Meta Connect on September 23 and 24 is the date to watch. A Meta-native option that ships free inside apps already installed on customers’ phones would undercut standalone vendors on distribution alone, regardless of how their underlying models compare.

TestingCatalog’s Alexey Shabanov reported the discovery on September 10, 2026.