microsoft/mxc

▲ 1,720 stars today★ 3,099⑂ 172

Policy-driven, layered isolation and containment

About microsoft/mxc

microsoft/mxc is an open-source project on GitHub, mainly written in Rust. Policy-driven, layered isolation and containment It currently holds 3,099 stars and 172 forks with 0 open issues, and was last pushed on an unknown date (repository created unknown).

Project Overview

Git Homed tracks it on the Today's Trending board.

GitHub Repository Details

Repository microsoft/mxc · default branch - · size 0 KB · watchers 0 · source: GitHub REST API and repository README

README

Microsoft eXecution Container (MXC)

MXC is a sandboxed code execution system for running untrusted code (model output, plugins, and tools) on Windows, Linux, and macOS. It provides multiple containment backends, from OS-native process sandboxes to full VMs, behind a unified containment model and typed SDKs.

Features

platform-appropriate containment backends security policies Bubblewrap, Seatbelt, MicroVM (NVX on Windows x64), Hyperlight, IsolationSession, and WSLC host filtering persistent containers container lifecycle operations

What is MXC?

MXC is an SDK dependency that builds into your app.

flowchart LR
    App["Your application
Launch API"] --> SDK["MXC SDK
Rust / .NET / Node
(in process)"] SDK --> Backend["Selected backend
(in process)"] Backend --> Container["Isolated workload
ProcessContainer / WSLC / Bubblewrap / ..."]

Your application specifies:

MXC validates the request, selects the backend, and launches the workload in the resulting container.

What container types are supported?

MXC runs workloads through platform-appropriate container backends on Windows, Linux, and macOS.

| Runtime platform | Default backend | Other backends | Minimum host OS | |---|---|---|---| | Windows 11 x64 / ARM64 | processcontainer | windows_sandbox\, wslc, microvm\, hyperlight\*, isolation_session | Windows OS-version support| | Linux x64 / ARM64 | bubblewrap | lxc, hyperlight | - | | macOS ARM64 / x64 | seatbelt | - | - |

\* These backends are experimental. MicroVM is currently available on Windows x64 only.

How do I use MXC?

Install an SDK through your package manager. You do not need to clone this repository.

| SDK | Package | |---|---| | Rust | https://crates.io/crates/mxc-sdk | | .NET | https://www.nuget.org/packages/Microsoft.Mxc.Sdk | | Node | https://www.npmjs.com/package/@microsoft/mxc-sdk |

The Node and .NET packages include the native runtime assets. The Rust crate builds the MXC SDK, engine, and selected backends into the consuming application.

Non-SDK consumption: Platform-specific executor binaries, such as wxc-exec.exe, accept JSON container-creation requests defined by the stable schema. Use for testing or when the SDK cannot be embedded in your app.

Running a contained workload

For complete SDK samples, see the Rust, .NET, and Node samples.

Sample Node snippet

import { spawn, type ContainerRequest } from '@microsoft/mxc-sdk/v1';

const request: ContainerRequest = { command: 'node -e "console.log(\'hello from container\')"', network: { egress: { default: 'deny' } }, timeoutMs: 30_000, };

const child = await spawn(request);

See the runnable streaming standard-I/O sample and the SDK API reference.

My application won't run in the sandbox!

Your application will hit access issues when running in a sandbox, until you've had time to tune your containment rules. We're here to help.

Debug console mode

Native executors normally reserve standard input, output, and error for the workload. Use --debug for MXC diagnostic output:

wxc-exec.exe --debug config.json

See MXC diagnostics for the complete developer reference.

Audit mode

Warning: --audit turns off all sandbox security for the workload being
analyzed. Never use it to run untrusted code.

Audit mode helps a policy author find access-denied failures and reconstruct a ProcessContainer policy that grants the files and capabilities a trusted tool actually needs. On supported Windows releases, run:

wxc-exec.exe --audit policy.json

MXC records the observed accesses and produces policy-authoring artifacts. See logging access denied for safe deny-and-record diagnostics, audit outputs, and supported workflows.

Telemetry

Official Microsoft builds send Required diagnostic data to Microsoft for the development 1.1.0-alpha request contract. MXC is moving to Required telemetry to keep MXC secure, reliable, and up to date: four events describe execution start and end, categorized failures, and process exits. They need no user consent or per-request opt-in, and administrative policy does not block them.

Published 0.9.0-alpha and 1.0.0 requests keep optional telemetry. It is off unless the run opts in, the Windows user has consented, and administrative policy permits collection. An administrator can block that telemetry but cannot grant consent for the user.

Local open-source debug builds are not configured to route telemetry to Microsoft. Windows release builds from source use the bundled signed telemetry component and are routed; set an empty MXC_TELEMETRY_COMPONENT_PATH to build without routing. Telemetry is a no-op on non-Windows platforms. See telemetry policy and consent for controls and privacy details.

Building from source

Build from source when developing MXC, changing the native runtime, or using the standalone executor binaries instead of a packaged SDK. Repository builds produce the platform-native runtime and executors and stage the native assets used by the Node SDK.

Build prerequisites are:

src/rust-toolchain.toml

Build

Windows

build.bat --all             # Release build for current architecture

Linux

./build.sh --all            # Release build

macOS

./build-mac.sh --all        # Release build for native architecture

Documentation

Consumer documentation

| Document | Repository location | Purpose | |---|---|---| | Terminology | docs/glossary.md | Plain-English definitions of consumer terms | | SDK samples | samples/ | Runnable Rust, .NET, and Node scenarios | | SDK API reference | docs/api-reference/ | Supported V1 operations and types | | Container lifecycle | docs/container-lifecycle.md | Persistent container lifecycle overview | | Logging access denied | docs/logging-access-denied.md | Diagnose blocked accesses and author policy | | Telemetry | docs/telemetry.md | Required diagnostic data and administrative controls | | Backend guides | docs/backends/ | Platform and backend prerequisites and behavior |

Repository contributors should start with the MXC development documentation.

Contributing

See CONTRIBUTING.md for contribution guidelines.

License

See LICENSE.md for details.

GitHub Stars & Activity

3,099Stars
172Forks
0Open issues
RustLanguage

GitHub Popularity

GitHub stars3,099
Forks172
Open issues0
Primary languageRust
License-
Stars gained today1,720
Created-
Last pushed-

Trending History

Monthly boardrank #96 · ▲ 1,720 stars

Related GitHub Projects

1

clash-verge-rev / clash-verge-rev

Rust★ 156,669⑂ 11,258▲ 246 stars
→
2

openai / codex

Rust★ 133,427⑂ 21,150▲ 172 stars
→
3

rustdesk / rustdesk

Rust★ 128,399⑂ 20,387▲ 139 stars
→
4

pbakaus / impeccable

Rust★ 104,331⑂ 6,187▲ 1,280 stars
→
5

vercel-labs / agent-browser

Rust★ 46,201⑂ 3,164▲ 150 stars
→
6

jdx / mise

Rust★ 35,854⑂ 1,527▲ 42 stars
→
7

longbridge / gpui-kit

Rust★ 19,542⑂ 1,214▲ 285 stars
→
8

vercel-labs / agent-desktop

Rust★ 17,619⑂ 1,255▲ 2,173 stars
→

More Trending Repositories