Try Microsoft MXC in a few clicks
MXC (Microsoft eXecution Container) runs AI agents and other software under a policy that Windows enforces. MXC Playground is a demo app for trying it: pick something to run, pick a policy, and see what it can and cannot reach.
Reel summary: The same six actions run first without a boundary, then under a process-container policy. The reel shows the resulting process and policy evidence, a governed agent doing its job, and how isolation sessions and WSL containers provide different boundaries.
If your network blocks the video host, watch the reel on YouTube.
Fifteen short steps in your browser. Click the app as you would live, or press the right arrow. Works best on a desktop.
Run the app on your own PC. Free, for Windows on x64 and Arm64.
MXC
Microsoft eXecution Container, from Microsoft
MXC runs a program under a policy that lists what it may read, write and reach. Windows enforces the policy from outside the process, so the software never has to cooperate. Version 1.0 has three kinds of boundary: process containers, isolation sessions and WSL containers. Developers build on it with SDKs for Node.js, .NET and Rust.
MXC Playground
A demo app built on MXC
Try MXC without writing code. Choose an agent, a script or an installed Win32 app, choose a policy profile, and run it with and without MXC side by side. Isolation sessions and Linux containers each have a page of their own.
What the walkthrough covers
The three kinds of boundary in turn, then your own software. Every result was captured on a real machine.
The same agent, contained
Six ordinary actions, run twice. Under a policy, the approved read and the workspace write still succeed. Everything else was never granted.
A governed agent doing its job
A clinical assistant reports its own boundary, then produces a recall worklist without reaching anything it was not given.
An account of its own
An isolation session gives the agent its own Windows account, with state that survives a restart. It sets who the agent is, not which files or network it can reach, and a side-by-side comparison shows the difference.
A Linux container
A WSL container runs Linux tooling from an image you choose. The policy’s folders are its only mounts, so the rest of the host does not exist inside it. Its network is either absent or fully open.
Your own software
Win32 applications and scripts installed on the machine run inside the same kind of boundary, with no rewrite and no SDK. Packaged (MSIX) apps cannot be contained.