Microsoft Execution Containers
ActiveMicrosoft's open-source, policy-driven containment layer for AI agents and untrusted code
Microsoft Execution Containers is a free, MIT-licensed containment layer: you declare in one JSON policy what an agent may touch, and a process, session, WSL or microVM backend enforces it on Windows 11, macOS and Linux. Conditional because the microVM backend is experimental, the session and WSL backends run only on Windows 11, and Claude Code support is only planned. The evidence we read is Microsoft's own announcement and repository, with no independent security assessment. It suits teams embedding agents in products.
Containment runtime that hosts third-party agents under a JSON policy; it runs no model itself.
Is it right for you?
Good for
- Declaring an agent's file, network, process and UI boundaries once in a JSON policy and enforcing it across Windows 11, macOS and Linux
- Finding out what an agent needs before locking it down: Learning mode blocks and records ungranted access in JSON reports
- Embedding containment in your own product through SDKs for Rust, .NET and Node.js under an MIT license
- Windows 11 setups that want a separate desktop and clipboard (session container) or a Linux environment (WSL container)
Not good for
- Hardware-backed isolation you can rely on today: the microVM backend is marked experimental
- Session or WSL containers on macOS or Linux: those backends are Windows 11 only
- Running Claude Code, Box, Egnyte, Perplexity or Raycast under MXC today: Microsoft lists them as planned, not shipped
- Judging isolation strength independently: the pages we read hold no third-party security assessment
Our experience
Pricing
Open Source- MIT license per the repository
- SDKs: Rust, .NET, Node.js
- No paid tier named on the pages we read
No verdict changes yet
The clock starts day one. Changes land here as our verdict evolves.
Sources
Verification log
- Profile· No changes
Automated agent
Want this running in your business?
We tested this tool and we build with tools like it every day. Tell us the workflow and we will set it up, integrate it and hand it over working.
The conversation runs on Gnosari, one of the tools in this directory. A real conversation, not a sales script.