Book An Audit
HomeAI Readiness AssessmentFreeHow We Start
Google Preferred SourceGet AiBuildrs in Search & AI Overviews
Book An Audit
← Back to Blog
technology

What Muse Spaces Are, and How They Change the Muse App

·By Jerry Jariwalla
A phone showing a custom tracker beside a notebook on a kitchen table

Muse Spaces are tools you describe in chat and the agent builds, added to the app on 6 Nov 2026. What is reported, and what is not yet confirmed.

Last Updated: November 2026

Muse Spaces are custom tools you describe in conversation, which the agent builds and can keep updated from your connected apps. Reporting places their arrival in the Muse app on 6 November 2026. One point is worth settling immediately, because it is widely confused: a Space is not the Muse Secure VM.

AiBuildrs builds custom AI systems for mid-market businesses. The team has completed over 200 successful AI implementations, producing $4.7M in documented client cost savings.

Described examples include trackers, planners, project boards and small games. You explain what you want in plain language, and Muse builds it rather than handing you a template.

One point to settle immediately, because it is widely confused. A Space is not the Muse Secure VM. The Secure VM is the computer the agent runs on. A Space is something the agent builds for you inside the app.

Key Takeaways

  1. A Space is a built tool, not a conversation: It lives in the sidebar and persists.
  2. You describe it, the agent builds it: Trackers, planners and boards are the reported examples.
  3. Connected apps keep it current: Spaces can refresh in the background rather than going stale.
  4. Sourcing is thin: Most available detail is secondary reporting, not an official page.

Those four points are what can be said with confidence. What follows covers each in turn, and ends with an honest split between what is confirmed and what is not.

What is a Space?

A Space is a custom tool the agent assembles because you asked for one in conversation. Rather than returning text, Muse produces something you can come back to.

Reported examples cluster around tracking and planning: price trackers, planners, project boards, and small games. The common thread is a thing with state rather than an answer.

Spaces are reported to live in the Muse sidebar, which is the structural point. A chat thread scrolls away. A Space stays where you left it.

This is also where the confusion with Muse Secure VM comes from, and it is worth separating properly. The Secure VM is the dedicated machine (2026) Meta assigns to each user, housing the agent and that person's data. A Space is a thing built on top, inside the app.

Mixing those two up produces articles claiming Meta named its virtual machine a Space. It did not, and AiBuildrs has seen that error in circulation already.

How do you create one?

By describing what you want. The reported flow is conversational rather than a builder interface with components to drag.

You explain the idea in chat, and Muse builds the tool from that description. Coverage also reports that Muse can create a Space on its own when you share an idea in conversation, without being asked explicitly.

That second behaviour is worth knowing about if you prefer to be asked first. It is the kind of proactive move consistent with how Meta describes the agent generally (2026), learning from conversations and returning with suggestions.

The practical implication is that a Space is cheap to attempt. If describing a tool takes a sentence, trying one costs very little.

A Muse SpaceThe Muse Secure VM
What it isA tool the agent builds for youThe machine the agent runs on
Where it livesIn the Muse sidebarBehind the product
You create it byDescribing what you wantNothing, it comes with Muse
Stays current viaYour connected appsNot applicable
Officially documentedNot fully, at the time of writingYes, in Meta's launch material
A described idea becoming a built tool in the sidebar, then refreshing from a connected app
A described idea becoming a built tool in the sidebar, then refreshing from a connected app

How does it stay updated?

Through the apps you have already connected to Muse. A Space linked to a connected service can refresh in the background rather than showing a frozen snapshot.

Reported examples include new concert dates appearing, price changes being picked up, and progress against a savings target moving on its own.

There is a condition attached that commentary has noted. Background updates depend on the agent reading app data while you are not in Muse, which is a permission question as much as a feature.

So the honest framing is that a Space is as current as the connections you have granted. A Space with nothing connected is a static tool you update yourself.

AiBuildrs treats that as the deciding factor when assessing whether a feature like this is useful or merely novel. A tracker that does not track by itself is a list.

What can you edit or pin?

You keep refining a Space after it exists. Reporting describes adding missing pieces, changing its appearance and changing its behaviour, with the agent revising it in place.

That iterative pattern is the part most like working with a person. You are not regenerating from scratch each time, you are asking for a change to something that already exists.

Sharing is less settled. Coverage indicates Meta is exploring ways to let people share Spaces, which reads as a direction rather than a shipped feature.

Treat anything about collaboration as unconfirmed for now. A tool you can share and one you are told might become shareable are different things to plan around.

What is official, and what is still unconfirmed?

This deserves a straight answer, because the sourcing here is weaker than for most of the Muse product.

Reasonably consistent across coverage: Spaces arrived in the Muse app in early November 2026. They are built from plain-language descriptions, they live in the sidebar, and they can connect to apps and refresh. You can iterate on them afterwards.

Not confirmed from an official page we could locate: the precise feature set, how sharing will work, and country-by-country availability. Coverage states Spaces are available everywhere Muse is, which is a claim worth verifying rather than repeating.

Actively disputed: some outlets describe Spaces as breakout conversations, others as persistent tools. Those are meaningfully different products, and the disagreement suggests at least one description is wrong.

The sensible position is to try it rather than read about it. AiBuildrs re-checks Meta's own pages before advising a client on any of this, because features announced in a week-old product move quickly.

Frequently Asked Questions

Is a Space the same as a chat?

Reporting is not unanimous here, which is itself worth knowing. Several outlets describe Spaces as persistent tools living in the sidebar, while others describe them as breakout conversations. Those are different things. The weight of coverage favours the persistent-tool reading, since the examples given are trackers and planners rather than discussions. Check the app directly rather than trusting either description.

Is a Space the same as Muse Secure VM?

No, and this confusion is common enough to be worth stating plainly. Muse Secure VM is the dedicated virtual machine Meta assigns to each user, housing the agent and that person's data. A Space is a tool the agent builds for you inside the app. One is infrastructure, the other is something made using it. Articles conflating the two are describing a product that does not exist.

Can I share a Space?

Not confirmed. Coverage indicates Meta is exploring ways to let people share Spaces, which describes an intention rather than a shipped capability. Until an official page says otherwise, plan on a Space being yours alone. That matters if your reason for wanting one is collaboration, since a tool you cannot share solves a different problem from one you can. Check the app rather than planning around an intention.

Do Spaces use my connected apps?

Yes, and that is what makes them stay current. A Space linked to a service you have already connected can refresh in the background, picking up changes like new dates or price movements. The condition is that background updating depends on the agent reading that app data while you are elsewhere. The permissions you granted determine how much a Space can actually do.

Is this available in my country?

Coverage states Spaces are available everywhere Muse is available, which moves the question to where Muse itself is offered. That has been reported inconsistently during 2026 and has changed as the product rolled out. Any country list in a blog post may already be out of date. Check Meta's own pages for the current position rather than relying on secondary reporting.

What can I actually build?

The reported examples are trackers, planners, project boards and small games, which suggests tools with state rather than one-off outputs. Anything you would otherwise keep in a spreadsheet and update manually is a reasonable candidate. What is not clear from available coverage is where the complexity ceiling sits, since no official documentation of limits was found. Try something small before assuming something ambitious will work, and treat the ceiling as unknown.

Does Muse build a Space without me asking?

Coverage reports that it can, creating a Space on its own when you share an idea in conversation. That is consistent with the agent being designed to be proactive and to return with suggestions. If you would rather be asked first, it is worth watching for during early use. Whether this behaviour can be turned off is not documented in anything we located.

How is this different from a spreadsheet?

Mainly that it can update itself. A spreadsheet holds what you last typed, while a connected Space can refresh from the services you have linked. The trade-off is control and portability. A spreadsheet is yours, works anywhere and can be audited line by line. A Space depends on the product continuing to exist, and on your connections remaining granted. Weigh that before moving anything important into one.

Did Spaces replace anything?

Nothing we could identify. Spaces appear to be an addition rather than a replacement, arriving about a week after Muse Voice, which added spoken interaction. That pace is worth noting in itself. A product shipping two significant surfaces in consecutive weeks is one where any written description dates quickly. This article included, which is why it carries a date at the top.

Should a business rely on Spaces?

Not yet, for anything that matters. The feature is weeks old, the official documentation is hard to locate, sharing is unconfirmed, and outlets disagree on what a Space fundamentally is. None of that makes it bad. It makes it early. Use it for personal organisation, and keep business-critical tracking somewhere you control until the picture settles. Early is not the same as unreliable, but it is not the same as settled either.

Where do I check what is actually true?

Meta's own pages, and the app itself. Everything in this article that is not attributed to Meta directly comes from coverage published within days of launch. Is the weakest kind of source for product detail. Opening Muse and looking at the sidebar will answer most of these questions faster and more reliably than any article written this month. That includes this one.

Executive Summary

A Space is a tool the agent builds from your description, living in the Muse sidebar rather than in a chat thread.

Spaces can connect to apps you have already linked, which is what lets them refresh on their own rather than showing a snapshot.

You keep refining them. Add a missing piece, change how it looks, change what it does, and the agent revises the Space in place.

An important caveat runs through this article. At the time of writing, AiBuildrs could not locate Meta's own announcement page for Spaces, so the detail below comes from coverage rather than documentation. Check Meta's pages before relying on specifics.

What Should You Do Next?

Open Muse and describe one small tool you would otherwise keep in a spreadsheet. That tells you more in five minutes than this article can.

If the tracking you need belongs in systems you own rather than a consumer app, talk to AiBuildrs about building it properly.

People Also Read

  1. Muse vs Meta AI: Product, Model, or Assistant?
  2. What Muse Secure VM Is, and How It Differs

About the Author

Jerry Jariwalla is the founder of AiBuildrs and creator of the Growth Signal Intelligence framework. With over 22 years in digital marketing and multiple successful business exits, Jerry has spent the past decade leading AI implementation programs for mid-market businesses across professional services, recruitment, membership organizations, and traditional industries. AiBuildrs has completed over 200 successful AI implementations using a workflow-first methodology and is trusted by leaders at YPO, Vistage, Tiger 21, and C12 executive peer organizations.

Expertise: AI Strategy, AI Implementation, Workflow Automation, Custom AI Development, Voice AI, Offshore Engineering, B2B Sales Intelligence, Mid-Market AI Adoption

Connect: LinkedIn

Disclaimer: This content is for informational purposes only and does not constitute professional business or technology advice. ROI outcomes vary based on industry, existing systems, and implementation commitment. Contact AiBuildrs for a consultation regarding your specific situation.

Jerry Jariwalla
Article by

Jerry Jariwalla

Jerry Jariwalla, Founder & CEO of AiBuildrs, builds custom AI infrastructure, voice AI, automation systems, and The AEO Engine. View Jerry Jariwalla's Full Profile →

Tags:automationai-development