Microsoft Execution Containers reach general availability
MXC lets Windows apps sandbox what an AI agent can touch at runtime (files, network, UI) with support already shipping in GitHub Copilot and OpenAI Codex.
Microsoft announced on 7 October that Microsoft Execution Containers (MXC) are now generally available, alongside support in Windows 365. MXC is a policy-driven layer for containing untrusted or model-generated code: a developer declares which files, network destinations and UI surfaces an agent can touch, and MXC enforces that at runtime, outside the agent’s own control.
There are four containment backends. Process containers run on Windows 11, macOS and Linux. Session containers, Windows 11 only, give an agent its own isolated desktop, clipboard and input. WSL containers run a Linux environment under Windows 11. An experimental MicroVM backend adds hardware-backed virtualization on Windows and Linux. Policies can run in Enforcement, Learning, or Permissive mode, the last two useful for working out what an agent actually needs before locking it down.
GitHub Copilot, OpenAI Codex, Replit, LM Studio and Nvidia’s OpenShell already support MXC; Anthropic’s Claude Code, Box, Perplexity and others have announced support is coming. Microsoft says Entra and Intune integration is next.
Why it matters: if you ship or operate a coding agent on Windows, this is a standard containment layer to build against instead of rolling your own sandboxing per agent. The isolation modes map directly onto that classic agent-safety question — what can this thing actually reach — rather than leaving it to the agent’s own judgement.