v1.2.0 - a fresh Windows PC for your AI agent

1.2.0 - real Windows machines for your agent

This release combines the clean-machine app-testing loop with:

• Native interactive-desktop readiness and screenshots tied to a specific capture/window.
• Bounded desktop recording, self-contained HTML playback, optional host-encoded MP4 and interrupted-frame recovery.
• Concurrent CLI/MCP shared state, cooperative desktop turns and generation-safe cleanup.
• Encrypted/authenticated TCP and offline-mailbox transport with boot identity and replay rejection.
• Verified incremental warm deployment: no-change transfers, mutation/deletion, rollback and explicit process restart.
• Conservative host-only dependency diagnosis and explicit, verified Microsoft runtime provisioning.
• MSIX/Appx/bundle input handling and real AUMID activation; live matrix specifically proves native and WinUI MSIX.
• An agent-led setup guide with checksum verification, per-client registration, backup/preservation and admin/reboot consent.
• Fresh real-app imagery, a recorded UIA demo and a published workflow SHA256/build-provenance trail.

The integrated v1.1.0-version preview passed 95 unit tests plus real offline/TCP/firewall CLI/MCP, capture/recording,
native clean-versus-provisioned, WinUI EXE/MSIX and WPF tests. The 1.2.0 release adds native Windows hosted unit/package
checks, executable onboarding/configuration regressions and verified ZIP/checksum provenance.
See measured compatibility;
app/runtime/hardware coverage is not universal.

The default never installs app prerequisites. A provisioned pass is labeled non-clean. Windows Sandbox requires
supported Windows 11 editions, virtualization and one free guest slot. Actual UAC/lock transitions were not
induced in the recorded proof; native mock denial tests cover those guards.

Published artifact verification

Source: b5ea2b2348c157581a3991dfc6064f19655e02d5. Hosted release build: 97 tests and portable parity/smoke passed.

ZIP SHA256: e0fb22207acf904bc1d8fb8da7c990f73554dbb9465c7e87a53c988eed2adecb (44,919,958 bytes). Downloaded public ZIP matched digest/sidecar and passed a fresh real offline Sandbox run with bundled Node and host Node absent from PATH: actual CLI/MCP, UIA/image, six-frame HTML recording, verified incremental deploy/no-op/mutate/delete/restart and owned teardown. No guest remains.

Current verification record.

Public ZIP network-on/TCP proof

The same unchanged public ZIP also passed a fresh network-on Sandbox run on 2026-11-07 UTC using bundled Node with host Node absent from PATH: authenticated TCP identity/tamper/replay/stale-epoch/version rejection, concurrent CLI/MCP commands and copies, UIA/image response, six complete recording frames/HTML, verified incremental deploy/no-op/mutation/deletion/restart and desktop-turn transfer. Owned guest teardown succeeded; wsb list is empty and the coordination lock is released.

Exact local evidence: work\public-release-proof\integration\on.json and work\evidence\release-public-on.log; run 20261107-065106, recording c58986e670b865193bae1071afa73375. Archive SHA256 remains e0fb22207acf904bc1d8fb8da7c990f73554dbb9465c7e87a53c988eed2adecb.

v1.1.0 - portable Windows ZIP and sbx doctor

What's new

• Portable Windows x64 ZIP (sandbox-mcp-win-x64-v1.1.0.zip): the sbx CLI and the MCP server with Node.js bundled. Unzip and run; no Node.js install needed. GitHub Actions builds and smoke-tests it.
• sbx doctor: checks whether this PC can run Windows Sandbox (edition, Windows build, feature on, virtualization, the wsb tool) and says exactly how to fix whatever is missing. Every other command points you to it when Windows Sandbox can't be reached.
• Onboarding in the README: download, sbx doctor, the one-line command that turns on Windows Sandbox, then your first run.

Try it

1. Download and unzip sandbox-mcp-win-x64-v1.1.0.zip anywhere (for example C:\tools\sandbox-mcp).
2. Run .\sbx.cmd doctor and fix anything it flags. If the Sandbox feature is off: in an administrator PowerShell run Enable-WindowsOptionalFeature -Online -FeatureName Containers-DisposableClientVM -All, restart, then open Windows Sandbox once from Start.
3. Run .\sbx.cmd run C:\Windows\System32\charmap.exe --open.

To use it from an MCP client, point the client at sandbox-mcp.cmd in the unzipped folder (see the README for the config).

Needs Windows 11 24H2 or later, Pro / Enterprise / Education. The ZIP is Windows x64 only; there is no ARM64 package yet.

sandbox-mcp 1.0

Fresh, throwaway Windows machines for testing your apps. sandbox-mcp drives Windows Sandbox through the wsb CLI and exposes it as an MCP server (21 tools) and a CLI (sbx). Every run boots a clean Windows 11, does its job, copies the results out and destroys the sandbox.

Three one-shot commands

• sbx run <app.exe|folder> / sandbox_run: does my build run on a clean PC? Copies the app in, launches it, takes screenshots, checks the event log for crashes, runs an optional test script and writes report.md. Exit 0 = pass.
• sbx install-test <setup.msi|.exe> / sandbox_install_test: snapshots the machine, installs, uninstalls, and reports what the installer added and what its uninstaller left behind (files, registry, services, scheduled tasks, autoruns).
• sbx detonate <file> / sandbox_detonate: what does this file actually do? Runs it with no network (by default) and full auditing, and reports the process tree with command lines, names it looks up, connections it tries, persistence it plants, screenshots and plain-language findings.

Step by step, for agents

Start, copy in, exec or launch, screenshot, click or type, native UI Automation (tree, act and wait on WinForms, WPF, Win32 and WinUI controls by name or AutomationId), app errors, snapshot/diff, copy out, stop.

Network modes

on, firewall (outbound blocked, attempts logged) and off (no adapter; the guest agent talks through a shared-folder mailbox).

Requires Windows 11 24H2+ Pro/Enterprise/Education with Windows Sandbox enabled and launched once (for wsb), plus Node 20+. See the README for setup, the MCP config and the agent skill.