Meta introduced spaces in the Muse app on November 6, 2026. A person can describe a small experience they want, such as a gift tracker, planning board or trivia game, and Muse builds it inside the app. The person can adjust the space while using it and return to it later. Meta says spaces are available wherever Muse is available. That is a different announcement from its November 5 voice and avatar rollout: spaces change what a user can make and organize inside Muse, while voice changes how a user interacts with the assistant. VIBPS has not used the feature firsthand.
How does someone make and use a Muse space?
Meta describes a prompt-led workflow: tell Muse the purpose of a space, then refine its appearance or behavior through further requests. A finished space can live in the sidebar or the main tabs, be hidden when it is not needed, and be scheduled to appear at a useful time. The company gives examples ranging from a school-events view to a music tracker, wedding planner, small-business order tracker and trip plan. These are product examples in Meta's announcement, not VIBPS-tested templates or proof that every user can build every example with the same result.
Meta also says a space can connect to the apps a person uses and update its information in the background. Users can check off items, add notes and edit content directly. The announcement does not specify which third-party integrations are available to every account, what permissions each connection requests, or how reliably every example works. Anyone using a space for sensitive messages, invoices or school information should review the actual connection and data controls before relying on it.
Can you publish a Muse space for other people?
Meta says it is exploring ways to share spaces with other people. Its November 6 announcement does not say that a public sharing or marketplace feature is available now. That distinction matters for makers: a personal, reusable experience inside Muse is not automatically an independently hosted app with a public link, an owner profile or an audience. A reader should not assume a space can be submitted elsewhere or followed by other Muse users until Meta specifies that capability.
Why does this matter for software makers?
Spaces make the boundary between using software and shaping software more visible. Instead of choosing only from fixed screens, a user describes a small workflow and revises it as their needs change. This is VIBPS's interpretation of Meta's release, not a claim that spaces replace custom apps or professional development. Reusable personal tools still need reliable data, clear permissions and a way to recover when a generated workflow is wrong.
VIBPS is the social network for software: makers publish apps they own, people can explore them and follow creators. Meta's spaces currently emphasize a personal experience inside Muse. If sharing arrives later, the interesting question will be how a private adaptation becomes something another person can understand, trust and return to. For now, the release establishes personal creation and organization, not a public social loop for spaces.
