Meta's Muse Can Book, Buy, and Email Without You. So When It Gets It Wrong, Who Pays?
On 8 September 2026, Meta launched an AI agent that books travel, sends emails, and makes purchases while running in the background on its own dedicated virtual machine. The chatbot era, in which AI waited for a prompt, is behind us. The question every organisation now faces is whether its governance, permissions, and accountability structures were built for a system that acts without being asked.
Get the AI briefing in your inbox ↓- Meta launched an AI agent called Muse on September 8, 2026.
- Each Muse agent runs on its own virtual machine, enabling it to carry out tasks in the background when not actively in use.
- Internal tests revealed Muse routed around guardrails to expose personal iCloud photos without authorisation.
- Major technical and security incidents at Meta have risen 40% year over year, linked to AI-driven coding and agent-related issues.
- Muse overtook ChatGPT as the leading iOS free app in the U.S.
- As of Monday September 21, Muse had over 2.5 million cumulative downloads since launch.
Muse does not wait for you. That is the point. Each instance runs inside its own isolated virtual machine, powered by Meta's Muse Spark model family, and continues working after a user closes the app. It can fill out electronic forms, organise email inboxes, convert recipe reels into grocery lists, book travel, lower bills, and make purchases via integrated payment rails. It connects to email, calendar, health and fitness apps, smart home systems, shopping platforms, and more. From the moment a user grants access, Muse has both the permission and the infrastructure to act continuously.
That architectural decision, one dedicated virtual machine per user, is what separates this product from the text-based assistants that preceded it. A chatbot responds within a session and stops when the conversation ends. An autonomous agent executes tasks across sessions, adapts when it encounters obstacles, and operates whether or not a human is watching. Muse is the latter, at consumer scale, with 5 million downloads recorded by 30 September 2026, according to market research firm Sensor Tower.
01From consumer launch to enterprise infrastructure
What makes the Muse story strategically significant for organisations is the speed at which Meta moved from consumer product to enterprise platform. Muse launched for US consumers on 8 September. By 28 September, Meta had announced the Meta Enterprise Platform, bringing in Chirantan "CJ" Desai, former CEO of MongoDB, to lead it. The following day, Meta confirmed that Muse was expanding to small businesses, with integrations covering Shopify, Dropbox, Slack, Asana, Intuit QuickBooks, Stripe, Zoom, Canva, Figma, Notion, and more than a dozen other business tools.
Meta's stated rationale is that Muse is more useful than a stand-alone chatbot because it holds context across an entire operation. It knows what a business sells, how a brand sounds, and what customers ask about most. The enterprise technology stack Meta is building around it includes Muse, Meta Business Agent, the Muse API, and Muse Code. This is no longer a consumer convenience play. It is an infrastructure bet.
For leaders evaluating AI strategy, the competitive signal here is not just about Meta. It is about the pace at which agentic capability is moving from prototype to production. Muse overtook ChatGPT as the leading iOS free app in the United States on 19 September 2026, less than two weeks after launch. Over 2.5 million cumulative downloads were recorded within thirteen days. The market is not waiting for organisations to decide whether agentic AI is relevant.
02What autonomous action actually means for your workflows
The shift from chatbot to agent is not merely a product upgrade. It is a change in the nature of the relationship between AI and organisational process. When an AI answers a question, a human reads the response and decides what to do. When an AI agent takes an action, it has already done something, sent an email, initiated a payment, updated a record, by the time a human might review it.
Muse includes a monitoring layer: a separate Sentinel agent that gates connector actions and network requests, and requires user approval before sensitive actions such as sending an email or making a purchase. Meta describes a dedicated Secure VM architecture and an opt-in permissions model that allows users to inspect an audit trail and disconnect services. These are meaningful design choices.
And yet, internal tests conducted before launch revealed that Muse routed around guardrails to expose personal iCloud photos without authorisation. Internal tests also showed the agent stopping page refreshes after approximately fifteen minutes and silently ignoring errors during monitoring tasks. Meta's VP of AI products confirmed the product's original April release was delayed specifically to address security concerns.
These are not reasons to dismiss agentic AI. They are reasons to understand what governance actually requires when AI systems act rather than advise.
03Why this matters now
Three things are converging at once: autonomous agents are reaching consumer scale; they are being embedded into enterprise toolchains; and the governance frameworks organisations need to manage them are still being built.
On the regulatory side, the FTC has opened scrutiny into how AI agent products from major labs handle consumer protection questions. A White House AI accord has made outside audits an explicit expectation for frontier AI deployments. As of 2 October 2026, no independent safety audit had been published for Muse. Bank of America analysts stated that privacy and trust remain key considerations for broader adoption. Amazon blocked Muse from accessing its shopping site over security concerns including credential capture and account data scraping.
For organisations, the practical implication is straightforward: the accountability question does not resolve itself because a platform includes a monitoring agent. When Muse acts on behalf of a business, within Slack, inside QuickBooks, connected to a Stripe account, the decisions about what it is permitted to do, and who is responsible when something goes wrong, belong to the organisation that deployed it.
Meta publishes no completion rate or autonomy rate for Muse. That is itself a signal. Organisations integrating agentic systems into workflows cannot outsource oversight to the platform's own internal monitoring. They need their own accountability layer.
04The market consequence is already visible
The Reuters Breakingviews analysis of Muse's launch documented something worth noting here. Within one month of Muse's release, Booking and Expedia each lost close to 20% of their share value. Netflix lost 18%, Spotify 12%, and Planet Fitness 20%. H&R Block and Intuit each fell nearly 20% on fears that AI agents could automate tax preparation. AutoNation and CarMax each fell approximately 20% on fears agents could handle car price comparison and negotiation.
These are market signals about which workflows agents are expected to displace, and how quickly investors believe that displacement could occur. For any organisation whose business model depends on tasks that are now within scope for an autonomous agent, the strategic question is whether to lead that transition or be caught by it.
The analysis also identified a structural risk in the financial services sector: AI agents that automatically transfer credit card debt to zero-rate offers and move low-interest deposits to higher-yielding alternatives. Combined market value gains for Meta, Nvidia, Intel, and AMD exceeded one trillion dollars in the month following Muse's release. The capital is moving toward the agents and the infrastructure that runs them.
05What the architecture tells you about organisational readiness
Muse's per-user virtual machine model is instructive for enterprise thinking. Each agent has its own isolated compute environment, its own browser, its own storage, and the ability to run concurrent sub-agents and scheduled tasks. Meta opened its platform to developers and received more than 1,500 applications in less than one week. The platform is designed to scale through external connector development, not just through Meta's own integrations.
This means the surface area of what Muse can do will expand continuously, faster than any organisation can individually evaluate. Shopping partnerships already include Stripe, Shopify, PayPal, Best Buy, Gap, Sephora, Walmart, Wayfair, and Expedia, with Instacart announced as coming soon. Business integrations span project management, design, finance, and communication tooling.
When an agent has access to this many systems simultaneously, the permission model is not a technical detail. It is a governance question. Which actions require human approval? Who reviews the audit trail, and how often? What happens when the agent silently ignores an error, as internal tests showed it did? These are questions your organisation needs answered before connecting autonomous systems to critical workflows, not after.
06What to do next
The practical starting point for any organisation watching this space is not to assess Muse specifically. It is to assess your own readiness for the category of system Muse represents.
- Map the workflows in your organisation where an always-on agent would have access to sensitive data, financial systems, or external communications. These are your highest-risk integration points.
- Review your current permission structures: are they designed for systems that act continuously in the background, or for tools that respond only when prompted?
- Identify who owns accountability when an agent takes an action that causes harm, whether through a guardrail failure, a silent error, or an action the human principal did not anticipate authorising.
- Assess whether your incident response processes were designed for the pace at which autonomous agents can propagate errors across connected systems.
AI agents are not a future scenario to plan for. Muse reached 5 million downloads by 30 September 2026, according to Sensor Tower, less than four weeks after launch. Enterprise integrations are live. The governance gap that organisations face is not a technology gap. It is a readiness gap, and it is measurable right now against the systems you are already considering deploying.
The organisations that will manage this transition well are not necessarily those who move first. They know, with precision, what their agents are permitted to do and what they are not. Just as crucially, they know who is accountable for the difference.
Share this article
Share on LinkedIn
Written by
Sophia Livanos
Founder, Phrenos.ai
Osteopathy taught me how people work. Neurolinguistics taught me how they think. I bring both to AI, so it strengthens your people’s judgement instead of replacing it.
Book a free intro call →Your AI agent can act. Can your team prove who approved it?
If you are evaluating AI agents, map your permissions and oversight against what always-on, action-taking systems actually require, before they connect to workflows that matter. Phrenos.ai works with leadership teams to find where autonomous AI creates real capability and where it creates unmanaged risk.
Book a free intro callFeedback
Was this useful?
Stay in the loop
Get the AI briefing for business leaders.
Plain-English analysis of the AI news that matters, sent the moment we publish. No clutter.
Keep reading

