What was announced
Pavan Davuluri, who leads Windows and Surface, announced the app at Microsoft's Windows and Surface event in San Francisco. The same announcement appears in Microsoft's Windows Experience Blog post, "Building Windows for hybrid intelligence," dated October 7, 2026. Microsoft framed the app as offering people more choice in the agents they can use on a Windows PC.
Muse is not new. Meta's own newsroom dates its introduction to September 8, 2026, and describes it as a personal agent that acts on goals rather than only answering questions. iPhone in Canada reports that it launched in the U.S. on iPhone, Android and the web on that date. Windows Report says Meta later brought it to the Mac as a native app, with access to files, messages, calendar, notes and mail when the user permits. Windows is the platform still waiting.
What MXC is
Microsoft Execution Containers (MXC) became generally available on Windows 11 on October 7. Organizations can define which files and networks agents may reach, and those policies are enforced at runtime.
Microsoft's Windows Developer Blog says MXC is a policy-driven execution layer for untrusted or dynamically generated workloads. Developers can use it to contain model-generated output, plugins, tools, an agent harness, or an entire agent. Microsoft stresses that the policy sits outside the agent's control, so the agent can't grant itself more access. Microsoft's example is a coding agent that can edit a website repository and read server configuration but can't change that configuration.
Containment options
Microsoft lists four containment backends:
| Backend | Availability | Notes |
|---|---|---|
| Process container | Windows 11, macOS, Linux | Lightweight. Uses AppContainer on Windows. |
| Session container | Windows 11 only | Separate Windows account and session, with its own desktop, clipboard and input. |
| WSL container (WSLc) | Windows 11 only | Linux-first agent toolchains. |
| MicroVM | Windows 11 and Linux, experimental | Hardware-backed isolation. |
Microsoft says each backend has distinct security properties, so workloads should be matched to the right one. It has not said which backend Muse will use.
Policy and admin controls
- Policy areas: MXC policies cover the container type, process launch settings, file system access, network connectivity and user interface access.
- Operating modes: Enforcement mode blocks ungranted access. Learning mode blocks it and records it in a JSON activity report. Permissive mode allows it but records it.
- Intune: Microsoft says Intune policy for MXC process containers on Windows 11 is coming "soon." It is not described as available now.
- Identity: Microsoft also says Entra will soon distinguish agent activity from user activity in Agent 365, and that Agent 365 controls will extend to local agents.
What is not confirmed
Microsoft did not give a release date, minimum Windows build or hardware requirement. It also didn't say whether the app arrives through the Microsoft Store or as a download from Meta, or what Windows pricing will be.
The Windows Club asks whether a Copilot+ PC will be required. The Windows Experience Blog post doesn't answer that. Windows Forum's earlier coverage notes that the blog gives no minimum build or hardware requirement and doesn't say whether the app will be in the Store or a download from Meta.
The Windows Experience Blog post also doesn't say which MXC backend Muse will use, what permissions it will request, or whether Intune or Agent 365 will manage it at launch. Don't read the enterprise controls in Microsoft's general MXC announcement as Muse-specific commitments.
How MXC and Muse's own architecture fit together
Meta describes Muse as running on Muse Secure VM, a dedicated virtual machine that holds the agent and the user's data. Meta says users decide how much access Muse gets. It also says Muse asks permission before actions such as sending messages or making purchases. Appauxin notes that Muse in a browser today runs in Meta's cloud and can't see anything on your computer.
A native Windows app with MXC suggests a different model, because MXC is about containing things on the device. Microsoft hasn't explained how a cloud VM architecture and local containment will work together. That means:
- You shouldn't assume the app runs entirely on-device.
- You shouldn't assume data stays local.
- You shouldn't assume the app can't reach anything beyond the PC.
Those questions are open, and the sources don't answer them.
Why this matters
The ecosystem signal is the real story. The Windows Club reads the announcement as part of a broader push to make Windows a platform where different AI agents run alongside Copilot. Microsoft lists OpenAI Codex, GitHub Copilot, OpenClaw, Replit, LM Studio, NVIDIA OpenShell and Unsloth AI as already supporting MXC. It lists Anthropic Claude Code, Box, Egnyte, Heidi Health, Hermes Agent, Manus, Perplexity, Raycast and Simular among those expected to follow. Adding a consumer agent from Meta widens that list beyond developer tools.
MXC limits damage but doesn't guarantee good behavior. A boundary can stop an agent from touching files or networks it wasn't granted. It can't make the agent's decisions correct inside the permitted scope. Whether a sandbox helps in practice depends on how tight the default policy is and how clearly users can see what they are granting. For Muse, those details haven't been published.
Microsoft has a stake in the framing. Microsoft is promoting Windows as "the most secure platform for agents," which is marketing language as well as engineering. MXC being generally available is a documented fact. Muse's integration being stronger or weaker than other agents' is not something anyone can judge yet.
What to do now
- Keep Windows 11 updated. Microsoft's own footnote says Windows Update is required and that features will roll out over time, with availability varying by device, market and silicon platform.
- IT admins: don't plan around Muse yet. Wait for the app's actual management story, including Intune, Entra and Agent 365 support, before writing policy.
- Developers: look at the MXC SDK. Microsoft says the SDK, configuration schema, documentation and samples are in the MXC repository on GitHub. Its Learning and Permissive modes are meant for working out a least-privilege policy.
- Be skeptical of third-party download pages. No official distribution channel has been announced, so unofficial "Muse for Windows" installers should be treated with suspicion. That is general security advice, not something the sources report.
Bottom line
Microsoft has confirmed a planned native Windows app for Meta's Muse, built with MXC integration. It hasn't given a date, requirements, a distribution method, or the permission model. Until Microsoft or Meta publishes those, the announcement says more about Microsoft's plans for agents on Windows than about Muse itself.