Meta adds persistent custom spaces to Muse Meta adds persistent custom spaces to Muse

A place to return to

Meta says users can revise a space through further instructions and schedule when it appears. Connected apps supply background updates. Sharing remains a future possibility. This shifts the unit of interaction from an answer to an ongoing workspace. A conversation can produce a plan once; a persistent interface gives the user a place to change and inspect it later. That makes the relationship between the displayed information and its original source a continuing product requirement.

An existing agent supplies the foundation

Muse itself predates this release. Meta introduced the personal agent on September 8, describing a dedicated cloud computer and browser for each user. The company said a separate Sentinel system checks outbound actions and requests permission when needed. Its launch account also described selectable access to connected services, the ability to disconnect them and an audit trail. Those are relevant foundations for a persistent interface: a workspace containing information from several services also depends on the permissions granted to those services. Its visible arrangement and its authority to act are separate properties.

Conversation and stored state are different

The November 5 voice announcement addressed another part of the interaction. Meta described interruptible calls and expressive avatars, initially rolling out in the United States. Calls work across mobile, web and Mac. Users can choose voice alone, an avatar beside the conversation or a full-screen view. The company described work continuing while someone speaks, with glasses and Muse Charm support planned later. Voice changes how a request enters the system. A saved interface changes how the person returns to its result. These are separate releases, not two names for the same feature.

Connectors came before the custom interface

Meta’s September 29 small-business expansion added skills and connections to services including Shopify, Stripe, Intuit QuickBooks and Slack. That announcement also described custom connectors for unsupported services. It said publishing, sending and spending required approval. A business workspace therefore sits on top of a pre-existing connection layer, rather than establishing access to every service by itself. For software teams, that separates three jobs: connecting a system, assembling a view of its records and authorizing a change. Success at one does not demonstrate success at the other two.

Stored information has its own controls

The original September introduction described credentials held in secure storage, outside the agent’s direct visibility. Meta also said users could opt out of model training and that conversations and virtual-machine data were not supplied to its advertising systems. Those are company descriptions of the underlying service, not a new privacy promise in the spaces announcement. A recurring workspace makes these existing controls more relevant because users may return to the same collected information repeatedly. The useful question is which permissions remain attached to that information after its presentation changes.