Meta is adding persistent, user-designed “spaces” to its Muse AI app, turning a prompt into a reusable interface for tasks such as planning, tracking and games. Announced Nov. 6, the feature is available wherever Muse is available, according to Meta; the company says users can connect apps so spaces refresh information in the background. The announcement describes a product capability, not evidence yet that integrations work reliably across every use case or that users will adopt these custom workspaces.

What Meta announced

Meta announced Spaces for Muse on Nov. 6, 2026. The company’s Newsroom post defines a space as a custom experience built inside Muse by describing an idea. Examples range from a holiday gift tracker and daily word game to a DIY project planning board. Meta describes each as part of the app that can be reopened, refined and positioned within the interface, rather than a one-off answer in a chat transcript.

The distinction is important: the product pitch is not simply that Muse can answer a request, but that it can help create a small purpose-built destination and retain it for later use. The independent report by The Verge likewise characterizes spaces as app-like experiences users can create and interact with in Muse. The Verge’s account independently confirms the core announcement and its examples, while details about functionality and rollout still ultimately trace to Meta’s own statements.

Meta says users can continue to alter a space by asking Muse to add missing elements, change its appearance or modify how it works. People may check items off, add notes and make edits directly in the space. The company says those changes remain when the user returns. This makes continuity central to the feature: users are meant to return to an evolving tool, rather than restart from a blank prompt each time.

From a prompt to a persistent space

Describe, inspect, refine

Meta’s described workflow starts with a natural-language idea. A user might ask for a planner or tracker, review the generated result and then guide revisions through follow-up instructions. That approach reduces the need to configure every field or screen in advance. It also puts a practical burden on the system: it must infer what the user means, produce a useful structure and respond appropriately when that structure needs adjustment.

The company does not publish in this announcement a technical specification for how a space is generated, what code or data model underlies it, or what guardrails determine its behavior. Nor does it provide comparative evidence showing how often a first attempt succeeds, how much editing is typically needed or how spaces perform against conventional apps. The safest description is therefore that Meta says Muse can build and iteratively customize these experiences—not that every idea becomes a dependable standalone app.

Choose where it appears

Spaces can be added to the sidebar or moved into Muse’s main tabs, hidden when they are not needed, and scheduled to appear at selected times, according to Meta. Its example is a weekly planner displayed during the workweek and replaced by weekend plans on Saturday. This is a meaningful interface element: a persistent creation is more useful if it can be found quickly and if the app can surface it when relevant.

Scheduling should not be confused with autonomous execution. Meta says when a space can appear; the announcement does not say the space independently completes a user’s plans or takes consequential actions without instruction. Similarly, moving a space into a tab changes its placement, but does not establish that the user can export it or run it outside Muse.

What the examples reveal

The examples span personal life, entertainment and work. A shopping hub might bring gift ideas, Instagram-save wishlists, Marketplace listings and buyer messages into one view. A school dashboard could identify events in school emails and add them to a calendar. Meta also lists music release and concert tracking, a wedding planner with RSVPs and vendor invoices, a trivia game, a podcast idea-and-script workspace, a small-business order tracker, a freelancer client hub and a travel itinerary planner.

These are illustrations supplied by Meta, not independently demonstrated integrations or guarantees that each listed data source is currently supported for every account. The company’s formulation is conditional: connect apps that you use, and spaces can draw on them. The announcement does not enumerate supported third-party services, eligibility requirements, permissions, geographic restrictions or whether each example is available at launch. Those omissions matter especially for dashboards that combine email, calendars, social saves, financial details or customer communications.

Meta says connected spaces can update in the background, with new concert dates, price changes or savings progress appearing without the user having to request each refresh. That is the feature’s strongest promise of ongoing utility. It also raises questions not answered in the launch post: refresh frequency, error handling, stale-data indicators, battery or data use, and how users can tell which connected source produced a particular item. Until those operational details are available, background updating should be treated as Meta’s stated capability rather than an independently measured service level.

Availability and rollout

Meta says spaces are available “everywhere Muse is available,” beginning on the announcement date. The Verge reports the same broad rollout language, including a rollout to all Muse users. That is stronger than a limited waitlist claim, but it does not reveal the exact country list, supported app versions, account prerequisites or whether distribution can take time to reach individual users. Users who do not see the feature should not infer from the wording alone that it is available in every market; the source statement is bounded by Muse’s own footprint.

The same Meta announcement says the company is rolling out specialized versions of its models to Muse, trained with learnings from Muse Wonder. Meta presents that work alongside the Spaces release as an effort to improve the overall experience. The post does not attribute specific measured Spaces outcomes to those models, and the launch material does not establish that model changes are the cause of any particular feature behavior. These are related product updates, not proof of a quantified improvement to the new interface.

Meta also says it is exploring ways for users to share spaces and collaborate. That phrasing is explicitly exploratory. Sharing and collaboration are not described as available launch features, so it would be inaccurate to present Spaces as a team workspace today. The immediate focus in the announcement is an individually customized Muse experience.

What remains unproven

Meta’s announcement is a product description, not an independent audit. It supplies use cases but no adoption figures, reliability metrics or user research. The Verge independently verifies the announcement’s timing and summarizes the feature; its report does not establish that integrations have been tested across the examples or provide performance measurements. A separate Unite.AI report also recaps the announcement, but its account is largely based on Meta’s post and is not a substitute for independent product testing.

There are also unanswered privacy and control questions inherent in the examples. Email, calendars, saved social posts, invoices and buyer messages may contain sensitive information. The launch announcement encourages connecting apps but does not detail data retention, how information is used to build or update spaces, permissions by source, deletion behavior, or whether content from a connection is used for model training. This article does not assume that a particular privacy policy applies to a specific integration; users should review the in-product permission prompts and Meta’s applicable terms before connecting sensitive accounts.

Another practical limitation is portability. A user may invest time shaping a space, but the announcement says it lives inside Muse; it does not promise export, interoperability or backup in another service. Likewise, users may expect an app-like experience to behave consistently. The announcement does not explain recovery when a connected source changes, when data is missing, or when the generated layout no longer fits a user’s needs. These are ordinary product questions, not evidence of a defect—but they will determine whether a saved space becomes genuinely dependable.

Why this matters for AI assistants

Spaces signal a shift in how an assistant can be packaged. In a conventional chat, the user asks and receives a response; in Meta’s envisioned pattern, the assistant helps make a repeatable interface that combines information, actions and an ongoing task. That could reduce friction for lightweight personal tools: a concert tracker need not be rebuilt in each conversation, and a planner can remain visible as dates change.

The same design sits between chatbots and conventional software. It asks whether people want to assemble small bespoke tools through conversation rather than choose an existing app, spreadsheet or template. The answer will depend less on the novelty of creating a space than on whether it is accurate, easy to revise, transparent about its sources and less work than the alternatives. Meta has not yet provided evidence that Spaces displaces existing services or improves task completion; those remain questions for real-world use.

For Meta, the feature may also encourage users to keep more routines inside Muse. Persistent planners and trackers can create repeat visits in a way that isolated answers do not. That is an interpretation of the product design, not a disclosed corporate objective. It also underscores why control over connections, visibility and deletion will matter: a helpful personal hub and a new dependency on a single assistant can be two sides of the same experience.

What to watch next

The most useful evidence will come from specifics Meta has not supplied in the announcement: a published list of supported connections, clear permission and data controls, explanations of update timing and a way to identify stale or conflicting information. Independent tests could assess whether the school-calendar example correctly filters relevant events, whether shopping details remain current, and whether users can modify or remove content without losing the rest of a space.

Rollout clarity will matter too. “Everywhere Muse is available” establishes Meta’s stated scope but not a country-by-country or platform-by-platform matrix. The company may also clarify how specialized Muse models relate to Spaces, and whether shared spaces graduate from exploration into a launched feature. Until then, the announcement supports a measured conclusion: Meta has introduced persistent, customizable experiences within Muse, with connected background updates among its proposed uses; broader claims about reliability, privacy outcomes or collaboration would go beyond the available evidence.

FAQs

What are Meta Muse Spaces?

Meta describes a space as a custom experience built inside Muse from a user’s idea. It can be saved, revisited and refined, with examples including planners, trackers, dashboards and games.

When did Spaces launch?

Meta announced the feature on Nov. 6, 2026, and says it is available wherever Muse is available. The announcement does not list country-level or platform-level rollout details.

Can Spaces update automatically?

Meta says that when users connect relevant apps, spaces can update in the background—for instance, with new concert dates or price changes. The announcement does not specify refresh schedules or reliability guarantees.

Can people share or collaborate on a Space?

Not as a confirmed launch capability. Meta says it is exploring ways to let users share spaces and build a collaborative experience.

Does the announcement explain privacy controls?

It does not provide a detailed account of permissions, retention or training use for connected information. Review the permissions and applicable terms shown in Muse before connecting sensitive services.

References