Skip to content
MustHave.ai Musthave.ai
AI Tools

Meta Muse Adds Custom Spaces and Starts a US Voice Rollout

Meta Muse adds custom Spaces wherever the app is available. Voice and expressive avatars are rolling out first in the US on mobile, web, and Mac.

Meta Muse Adds Custom Spaces and Starts a US Voice Rollout
Hoodie Seal holds a purchase at an approval gate while checking the action before it can pass.

Muse can keep a task running after you close the app. The newer Spaces feature gives you a place to return to the work.

Muse began rolling out on September 8, 2026, in the United States via iOS, Android, and muse.ai. Meta says AI glasses support is coming soon. This is a consumer agent product, not the Muse Spark model or the Muse Code coding agent already covered by Musthave.ai.

Spaces are available where Muse is offered; voice starts in the US

On November 6, Meta introduced Spaces, custom tools built inside Muse from a description. Meta says you can pin a Space in the sidebar or main tabs and connect apps to keep it up to date. Spaces are available wherever Muse is offered. Meta says it is exploring sharing; it hasn’t announced shared Spaces.

The November 5 voice and avatar announcement describes a US rollout on mobile, web, and Mac. Meta lists voice conversations on its glasses and Muse Charm as forthcoming. If voice is missing, check your account’s rollout status before treating it as a device problem.

A gift tracker is a useful first Space. Create it with sample items, close Muse, and reopen it to see what it remembers. Connect a service only after you know which information you want the Space to refresh. We have not tested the new features.

Meta Muse can act after the app closes

The defining product change is continuity. A user can ask Muse to research, compare options, work through a browser, use a connected service, or prepare a transaction, then leave the app while the task continues. That makes Muse closer to a delegated worker than a chat response.

Continuity also expands the risk window. A wrong assumption can survive longer, a connected account can expose more data, and a delayed action may execute after the user has changed plans. Useful agent design therefore depends on interruption, approval, audit, and revocation controls.

What was available at the September launch

CapabilityLaunch statusImportant limit
iOS, Android, and web accessRolling out in the USBroader geography was not announced
Browser and connected-app actionsAvailable in the launchPermissions vary by action and service
Stripe Link paymentsAvailableUses one-time-use cards and Link protections
Shop Pay and 1PasswordComing soonNo final availability date in the announcement
AI glasses supportComing soonNot part of the initial app and web rollout
Confidential VMPlanned later in 2026Not a launch-day protection
Status is based on Meta’s September 8 launch announcement. Coming features should not be treated as currently deployed.

Muse uses a Secure VM and a separate Sentinel agent

Meta says each Muse task runs in a dedicated Secure VM. A separate Sentinel agent evaluates proposed internet actions and can require user approval before sensitive steps. Muse also provides an audit trail so a user can inspect what happened.

These are Meta-reported architecture and policy claims, not an independent security audit. The practical test is whether Sentinel blocks the right actions, whether the audit trail includes enough detail to reconstruct a task, and whether revoking a connection stops work already in progress.

Purchases introduce a different approval boundary

Stripe Link can supply a one-time-use card and purchase protections without exposing a reusable payment credential to the agent. That reduces one risk but does not answer every commerce question. A buyer still needs to confirm merchant, item, quantity, price, delivery address, return policy, and final total.

  • Require approval immediately before the final purchase action.
  • Show the merchant and total on the approval screen, not only in the audit trail.
  • Set a low spending ceiling for early tests.
  • Confirm cancellation and return handling before delegating repeat purchases.
  • Revoke payment and account connections after a sensitive one-off task.

Meta’s privacy promises need precise reading

Meta says Muse conversations and Secure VM data are not shared with its advertising systems. It also says users can opt out of having their interactions used for model training. Those statements describe the current product policy. They should not be expanded into a claim that no operational logs exist or that every connected service follows the same policy.

Before connecting email, files, calendars, shopping accounts, or social accounts, check data retention, deletion, export, and revocation behavior for both Muse and the connected service. Our Meta AI recurring-task checklist provides a useful permission inventory.

Muse pricing is still incomplete

Meta says Muse is free for most needs and that subscriptions will support heavier use. The launch announcement does not publish a complete price table, quota schedule, or overage model. That makes cost comparison premature.

Do not build a workflow around the word free. Record task limits, wait times, connector availability, purchase limits, and any subscription prompt during real use. A useful agent budget includes the subscription, time spent correcting work, and the consequences of a wrong action.

How Muse differs from Meta’s other Muse products

Muse is now an overloaded name. Muse Spark is a model story. Muse Code is about delegated software work. The new Muse is a consumer personal agent with browser, app, messaging, and commerce actions. Readers should verify which product a feature or price belongs to.

A safe first-week test

  1. Start read-only: ask Muse to research and compare without sending or buying.
  2. Connect one low-risk account: avoid a full bundle of email, cloud storage, and payment access.
  3. Trigger an approval: verify exactly what information appears before an action.
  4. Interrupt the task: close the app, return, cancel, and confirm that execution stops.
  5. Inspect the audit trail: compare the record with what changed externally.
  6. Revoke access: confirm that tokens, sessions, and saved payment permissions are no longer usable.

My verdict: Muse is an action product, not just a chatbot

Meta Muse matters because it combines persistent work, connected services, and payments in a mass-market product. The Secure VM, Sentinel review, audit trail, and one-time cards are thoughtful controls. They still need to work amid interruptions, ambiguous instructions, compromised pages, and shifting user intent.

Use the initial rollout to test the approval boundary, not to maximize the number of connected accounts. If Muse makes its actions understandable and reversible, it can become useful. If the user cannot tell what it will do next, the convenience is not yet worth the authority.

Read the primary source

The September 8 launch announcement describes the original payments and security features. The November releases cover Spaces, voice, and avatars.

Abdessalam Alaoui

I'm Abdessalam Alaoui, founder of Musthave.AI. I write practical guides to AI models, tools, generative media.

Join the discussion

Your email address will not be published. Required fields are marked *

Keep reading

All news