Meta announced Muse on September 8, 2026 as a personal AI agent. The announcement describes Muse Spark as its underlying model and a dedicated cloud computer for browsers, connected apps and continuing work after the application closes.
Figure 1: Drawn from Meta architecture descriptions; AI Beyond has not validated isolation or approval behavior.
Separate product, model and coding agent
Muse is the personal agent product. Muse Spark is the underlying model named in the announcement. Muse Code is a separate coding-product name. Model research, open-weight news and terminal coding tools should not automatically be described as features of the personal app.
Confirm the entry through Meta's announcement and product page, which link to muse.ai. This overview concerns Meta's product rather than unrelated services sharing its name. Recording these identities separately avoids treating a model update as immediate availability of every feature to every user.
Tasks can cross several applications
Meta describes research, arrangements, email drafts or sending, and shopping. The workflow reads authorized information and advances through browsers or apps before reporting back. Usefulness depends on connected services, access scope and verifiable outputs rather than fluent text alone.
We recommend starting with checkable, reversible work: organize public sources with citations and missing information, or draft an email while retaining the sending step. Specify sources, recipients and unfinished items. These are editorial trial suggestions, not successful Muse tasks observed by AI Beyond.
Cloud execution and Sentinel
Meta describes Muse Secure VM as a dedicated cloud computer, with a separate Sentinel that reviews outgoing actions and seeks permission when needed. The product also provides a record of completed and planned actions. During use, check system permissions and each external action.
The launch announcement describes Confidential VM as a future plan, so it should not appear as a generally available current feature. Meta says conversations and VM data are not shared with its advertising systems and offers controls concerning model improvement. Consult current privacy terms and account settings for processing details.
Mac access has two layers
At the check date, Meta help documents Mac support involving Full Disk Access, Automation and Notifications. It separately describes per-app choices: off, read only, and read and interact. Operating-system permission and the agent's in-app access setting are different layers.
You can change app access in Muse and revoke system permissions in macOS Privacy & Security. The help page warns that agents may make mistakes or take unexpected actions; monitor action records and stop the task when needed.
Check the scope necessary for a folder task before granting broader access. Review recipients, contents and amounts for external communication or purchases. The computer-use permission guide separates system, application, account and external-action controls.
A first-trial sequence
- Confirm regional and account eligibility through Meta's official entry and check current platform downloads.
- Review data and memory controls, connecting only services required for the task.
- On Mac, inspect both system permissions and Muse's per-app choices.
- Give a research or draft task with output format, source requirements and prohibited actions.
- Check the result and available action records before expanding write access or external actions.
- Disconnect unused services or revoke system access when appropriate.
Use the options shown in your account, paying particular attention to Muse’s own permission settings.
Regions, platforms and pricing
The September 8 launch describes rollout in the US across iOS, Android and web, with AI glasses planned. Separate Mac help exists, but documentation does not establish download eligibility for all accounts or regions. For access outside the US, check the current download and registration options.
Meta’s launch describes free access for most everyday needs and subscriptions for greater usage. Before paying, check the allowances, features and terms in your account; payment services may have additional conditions.
Choosing among Muse, Cue and Manus
Cue, from Manus, emphasizes agent identity and collaborative teams and is currently invitation-based early access. Manus 2.0 emphasizes Studio environments for creation, development and automation. Muse emphasizes connected personal applications and cloud tasks, with separate Mac permission help.
Feature descriptions alone do not establish a performance winner. Check eligibility, information scope and permissions, then use the same task to assess delivery. Start with Manus's relevant environment for video timelines or game development. For tasks across personal apps, verify exact service support in Muse and Cue rather than assuming identical connectors.
Our current recommendation
Muse is a candidate for eligible users who can define tasks, manage permissions and verify outputs. Before unattended communication, file changes or payments, establish confirmation rules, action records and recovery options, then expand gradually. Access without acceptance criteria can turn organization work into troubleshooting work.