Meta introduced Spaces in Muse on 6 November 2026. According to its announcement, users describe an idea to create an interactive experience, then edit it and return later. Spaces can sit in the sidebar or main tabs and appear on schedule; connected apps can supply background updates.
Availability is limited to places where Muse is available. Sharing and collaboration remain exploratory. The announcement does not specify granular connector permissions or retention rules.
For connected data, read the general Muse disclosures separately. Meta’s September 8 safety description says sanitized inference data can be used for training, with an opt-out, and read/write access is separated where the underlying service supports it. These are general Muse disclosures, not new Spaces-specific guarantees.
Start with a task you can check by hand
A useful first trial should be easy to verify and cheap to abandon. We suggest a packing checklist with invented items, rather than customer records, school messages or financial information. That keeps the initial question simple: does the interface behave the way you asked?
A proposed first prompt: Create a packing checklist using five sample items. Let me mark an item as packed and show completed and total counts. Do not connect any apps.
This is an example for evaluation, not a tested recipe or a promise that a particular generated result will work.
Look beyond the first screen
- Change the data: add an item, delete one and try two items with the same name. Compare the displayed totals with your own count.
- Return later: close and reopen the experience. Check which edits remain, rather than treating an attractive preview as proof of persistence.
- Change one requirement: ask for a different grouping and check that earlier items and completion states are still correct.
- Decide what access is necessary: before connecting an app, read its actual permission request and applicable data settings. Stop if the requested scope exceeds the task you intended.
Keep the original checklist elsewhere during a trial. If you later consider a more important workflow, define what needs human confirmation and how you will notice stale or missing information. We have not tested Muse Spaces; these are proposed acceptance checks for deciding whether a generated tool earns a place in your routine.