Skip to content- Sources: primary, discussion
- Summary: The post says that coming by the end of the month, GitHub Copilot will decide when a task is best handled by on-device intelligence, running MAI Code 1.1 Flash at 137 billion total and 6.8 billion active parameters in a 53 GB quantized form on NVIDIA RTX Spark Windows machines such as Surface Laptop Ultra. Separately it describes tool execution inside Microsoft Execution Containers, backed by ProcessContainer on Windows, Seatbelt on macOS and bubblewrap on Linux. The post states that built-in file tools are checked in process rather than isolated by the operating system, and that remote MCP servers sit outside the sandbox.
- Why it matters: A vendor is committing to OS-enforced isolation for agent tool calls, which is the mitigation class the 2026 coding-agent sandbox escapes pointed at, with two stated gaps already inside the boundary it claims.
- Follow-up: Whether in-process file tool checks and remote MCP servers move inside the sandbox boundary, tracked with the open coding-agent sandbox escape thread.