Meta Muse

Executive Summary

Muse is Meta's consumer agent for getting personal tasks done across a persistent cloud computer and connected services. Launched September 8, 2026, it uses Muse Spark and can browse, prepare documents, arrange tasks, and return for approval when an action needs attention. The initial rollout is in the US through iOS, Android, the web, and WhatsApp. This profile checks public evidence as of September 16, 2026.^[1]

Its useful distinction is continuity: a person can develop a goal, let work continue, and review the resulting actions or artifacts later. The tradeoff is the scope of access and memory that makes this possible. Evaluate the permissions, data settings, and review effort alongside the convenience. This is a source-based assessment, not a hands-on security test or a claim that Muse reliably completes every advertised task.

---

Product Overview

Muse uses a continuing main conversation alongside focused side conversations. Goals capture work that extends beyond a single answer; Ideas surface possible next steps, with controls over proactive behavior. Its artifact workspace can hold documents, PDFs, web pages, and dashboards. Those surfaces matter because reviewing a completed file or proposed action is different from reading a confident chat response.^[5]

Key Capabilities

Product Surfaces

A Concrete Evaluation Workflow

A useful first trial is a bounded weekly planning task: connect the relevant calendar, identify upcoming commitments, produce a private checklist, and request approval before changing an event. Muse's connector documentation supports calendar-aware proactive work and configurable read/write access. If Facebook, Instagram, or Threads share the same Accounts Center, Meta says those services connect automatically; review that account grouping before treating the setup as entirely manual.^[6]

Evaluate the result against the original calendar: missing events, incorrect time zones, duplicated reminders, and unauthorized changes are separate failure modes. Then revise an instruction and check whether subsequent work follows it. This is a proposed evaluation, not a task performed for this report.

---

Technical Architecture

Meta describes a persistent Linux environment with storage, browser tools, scheduled jobs, and subagents. Its technical account places the Hatch agent in a restricted Debian systemd-nspawn container, while connector services, credential storage, and safety components sit outside that container. Sentinel controls connector actions and network egress. Credentials use surrogate values that are replaced at the network boundary, limiting direct model access to real secrets.^[8]

This is a layered boundary: containing execution and deciding whether an action is authorized are different jobs. Meta also describes process taint tracking and separate approval handling. These are architectural claims from the operator, not independent verification of every path. Confidential VM remains a planned later-2026 enhancement; the current deployment does not establish that Meta itself cannot access the environment.^[8]

Permissions Are Part of the Workflow

These controls are documented in the permissions guide. A broad persistent grant is meaningfully different from approving one email, and allowing a website is not proof that the site is trustworthy. Review scope as well as the immediate proposed action.^[9]

Custom connectors expand the integration surface, but Meta says it does not review those connectors or how they use information. Disconnecting a service stops further exchange; previously acquired context can remain in memory or conversation history. Teams should distinguish credential revocation from data removal.^[6]

Memory, Training, and Deletion

The privacy policy says Muse conversations and VM data are not shared with Meta's advertising systems. It separately enables model-improvement use by default, with an opt-out that applies to past interactions. These are separate policies: an advertising exclusion does not mean no training use. Accounts Center choices also affect how other account information may be combined.^[10]

Muse's data controls expose editable memory files, including Memory, Soul, and Identity documents. Users can export chats and manage stored files and goals. Deleting a conversation does not necessarily erase information already learned from it. The Forget skill attempts to find and remove related information, whereas Reset permanently removes history, files, and active tasks. Check the relevant control rather than assuming all deletion buttons have the same effect.^[11]

---

Strengths

• Low operational burden. The consumer manages tasks and access rather than provisioning an agent host. That makes a small personal trial easier than operating an always-on server.
• Inspectible work. Goals, artifacts, activity, and approval cards give the user several places to inspect what the agent intends and produced.^[5]
• Explicit permission choices. Different approval scopes let users begin narrowly and expand access when the workflow earns trust.^[9]
• Documented memory controls. Editable memory and export controls create a practical way to inspect and correct persistent context.^[11]

Cautions

• Early evidence. Launch demonstrations and short trials do not establish long-term completion rates, incident recovery, or reliability across every connector.
• Permission is not correctness. A user may approve an inaccurate draft or a poorly chosen action; approval quality still depends on what is shown and reviewed.
• Current privacy boundary. Confidential VM is future work. Judge the service on the architecture and policies available today, not an announced stronger design.^[8]
• Training defaults require attention. Disabling model improvement is a separate decision from connecting services or preventing advertising use.^[10]
• Consumer responsibility remains. Muse terms require oversight and place responsibility for authorized use on the user. They do not provide a guarantee that generated content or automated actions are accurate.^[2]

---

What Users Say

Eric Hal Schwartz, TechRadar, September 14: his first-hand trial found useful assistance alongside discomfort with expanding access. A shopping task reached an account-login boundary; an inbox review found an overlooked utility appointment and prepared a response for approval, but also inferred a distorted picture of him from promotional email. The useful lesson is to inspect both task output and the assumptions inferred from connected data. This is one journalist's experience, not a measured failure rate.^[12]

Scott Loftesness, September 10: a two-day account describes recurring briefings and research alongside friction with file organization and a misunderstood keyboard question. The post explicitly says Muse drafted and published it. That provenance makes it evidence of a user's configured workflow with AI-assisted narration, not independent verification of every claim or a substitute for a longer reliability study.^[13]

---

Pricing & Licensing

Official subscription terms checked September 16, 2026:

Meta says availability and benefits vary by account and region, and subscriptions renew monthly until canceled. These are Muse tokens, not a documented number of completed tasks or a directly comparable provider API-token budget. The public page does not quantify the free allowance. Confirm the offered plan during onboarding rather than extrapolating from a press headline.^[3]

Licensing model: proprietary service; users retain rights to their content subject to the service's operational license and applicable policies. This is not an open-source runtime offered for self-hosting.^[2]

Additional costs: paid connected services and authorized purchases are distinct from an agent subscription. A sensible evaluation measures the time saved after review and correction, rather than treating a large token allowance as proof of value.

---

Competitive Positioning

Muse is a particularly relevant candidate when the desired workflow combines personal goals, conversational continuity, mobile access, and an agent-managed browser. A business evaluating regulated data, shared ownership, or employee lifecycle controls should independently establish those requirements; consumer convenience does not establish enterprise suitability.

---

Ideal Customer Profile

Best fit: adults in the current rollout who can begin with a bounded task, inspect outputs, and make deliberate choices about connected accounts and memory.

Poor fit: users who require offline operation, self-hosting, a guarantee of no provider access, or unattended high-consequence decisions. Those needs should be requirements established before adoption, not assumed from a “secure computer” description.

Viability Assessment

Muse has a concrete launch, live application distribution, paid subscriptions, and detailed help and architecture materials. That is stronger evidence of an operating product than a concept demo, but the public window reviewed here covers little more than its first week. This research did not establish representative retention, production reliability, or independent penetration-test results. The appropriate next evidence is repeated task completion and recovery under ordinary use, rather than launch attention alone.^[1][7]

Bottom Line

Muse deserves evaluation as a personal cloud agent with useful continuity and visible controls. Start with a narrow recurring workflow, inspect memory and data settings, and expand permissions only when the observed result justifies it. The strongest unresolved question is how much reliable work remains after review, corrections, and access management.

Recommended for: supervised personal administration and research trials.

Not recommended for: workflows whose requirements depend on an unshipped confidentiality guarantee or unverified autonomous reliability.

Outlook: promising product direction, with reliability and trust to be demonstrated over sustained use.

---

Research by Ry Walker Research • methodology