JigRig

Drives Windows desktop apps inside an isolated Windows Sandbox, so UI automation can run while you keep using your machine. Every synthetic click, drag and keystroke lands in the guest; your mouse, keyboard, clipboard and windows are never touched. Ships an MCP server for agents and a diagnostics window.

At a glance

What it is
A local stdio MCP server (JigRig.Mcp.exe) that starts an isolated Windows guest, deploys an app into it, and forwards Jig's UI Automation tools into the guest as vm_* tools. Fourteen rig_* tools manage the guest (rig_up, rig_deploy, rig_launch, rig_logs, rig_reset and others).
Best for
Letting an AI agent UI-test or explore a Windows app (WPF, WinForms and similar) on a clean desktop that is thrown away afterwards, while you keep working.
Not for
Driving apps on your real desktop or in your signed-in browser (that is Jig); apps that need host hardware, a host-resident session or licence; machines without Windows Sandbox or Hyper-V; macOS or Linux.
Requirements
Windows Pro, Enterprise or Education (developed on Windows 11) with hardware virtualization and either the Windows Sandbox feature or Hyper-V; the .NET 10 Desktop Runtime. The built-in doctor checks all of it and says which requirement fails.
Administrator rights
Installing JigRig is per-user. Turning on Windows Sandbox or Hyper-V is a one-time Windows feature change that needs an administrator and a restart, and the Hyper-V provider needs one UAC prompt to build its VM.
Isolation
The boundary is Microsoft's (Windows Sandbox, or a Hyper-V VM). The configuration JigRig writes maps one host folder into the guest as read/write, leaves networking on by default, and turns clipboard, audio, video and printer redirection off.
Record
Every rig_* and vm_* call is written to a transcript on the host, with failure screenshots.
Status
Pre-release (version 0.0.1-dev), an independent project. Hundreds of unit tests; no changelog or published license yet; a binary download with no source link published here.

Install

Run in PowerShell:

irm https://shakytext.com/jigrig/install.ps1 | iex

That installs the host tools to %USERPROFILE%\JigRig\bin, stages the guest payload into %USERPROFILE%\JigRig\share, and registers the MCP server with Claude Code as jigrig when its CLI is present. Re-run the same line any time to update; your configuration, deploys and reports are left alone.

Or grab the payload directly (extract both into one folder): Host tools · Guest agent · README

Is it a good fit?

Choose JigRig when

Look elsewhere when

Check first, then use

Windows Sandbox needs Windows Pro, Enterprise or Education, hardware virtualization, and the Sandbox optional feature. A managed machine can also block mapped folders or networking by group policy, which stops the rig outright. Run the doctor before anything else:

%USERPROFILE%\JigRig\bin\mcp\JigRig.Mcp.exe --doctor

It reports every requirement with the value it actually saw and, where one exists, the fix. Add --fix to apply the automatic ones, or run bin\doctor\JigRig.Doctor.exe for the same checks with buttons. Requires the .NET 10 Desktop Runtime; the installer offers to fetch it via winget when missing (winget may ask for administrator rights).

Page last updated 2026-10-19. JigRig is a separate install from Jig, which drives your real desktop; JigRig bundles its own copy of Jig for the guest. The README has the lifecycle, the things worth knowing, and the Hyper-V option.