build-openshell-mxc-windows

Maintains and validates OpenShell's build-only Windows MSVC lane for x64 and ARM64 targets.

8.5k|1.3k|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/NVIDIA/OpenShell --skill build-openshell-mxc-windows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-openshell-mxc-windows
Source: https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/build-openshell-mxc-windows
Command: npx skills add https://github.com/NVIDIA/OpenShell --skill build-openshell-mxc-windows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OpenShell must compile and test on Windows MSVC for x64 and ARM64 without accidentally enabling unsupported runtimes like Docker, Kubernetes, Podman, or VM backends. This Skill keeps that build-only Windows lane working, validated, and correctly reported.

Core Features & Use Cases

  • Windows MSVC Validation: Runs windows:* mise tasks for x64 and ARM64 check, release build, and native workspace tests through the Visual Studio developer environment.
  • Unsupported Driver Contracts: Keeps Docker, Kubernetes, Podman, and VM drivers excluded from Windows builds while verifying they return clear unsupported errors via focused contract tests.
  • Build Reporting: Produces structured reports covering test counts, skipped or cfg-gated tests, artifact sizes, and SHA256 hashes for openshell-gateway.exe and openshell.exe.
  • Use Case: After modifying Rust code in the OpenShell repository, run the x64-host windows:ci lane to confirm the gateway and CLI still compile for both architectures and that unsupported drivers remain properly gated.

Quick Start

Ask the agent to run the OpenShell Windows MSVC validation lane on your checkout and report the check, build, test, and artifact results for your host architecture.

Frequently Asked Questions about build-openshell-mxc-windows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build OpenShell for Windows with MSVC?

Run the mise Windows tasks with --skip-tools, such as windows:check:x64, windows:build:x64, and windows:test:x64. The PowerShell wrapper enters the Visual Studio developer environment, adds rustup targets, and invokes Cargo with logs written per architecture.

How do I cross-compile OpenShell from x64 Windows to ARM64?

Use windows:check:arm64 and windows:build:arm64 on an x64 host with the ARM64 MSVC tools, Spectre-mitigated libraries, Clang tools, and CMake tools installed. The wrapper adds host-native LLVM and Ninja to PATH while bundled Z3 builds with native MSVC cl.exe.

Does OpenShell support Docker or Kubernetes on Windows?

No, Windows is a build-only target and Docker, Kubernetes, Podman, and VM runtimes remain unsupported. Their driver crates are excluded from Windows workspace targets, and gateway construction returns a clear unsupported error verified by focused contract tests.

Why does the ARM64 Windows check fail when x64 passes?

Common causes include missing ARM64 MSVC or Spectre-mitigated libraries, missing host-native clang-cl or Ninja, or CL and _CL_ variables injecting MSVC options into clang-cl. The wrapper deliberately avoids setting CL or _CL_ for this reason.

Why do focused unsupported-driver tests show many filtered-out tests?

This is expected because Cargo runs one named test, windows_builtin_compute_drivers_report_unsupported, and filters the other openshell-server tests. Report these as filtered, not ignored, and treat package-level excludes separately since Cargo does not print them as ignored.