In January 2026, Microsoft announced the public preview of the WinApp CLI, a new command-line tool intended to consolidate common Windows application development tasks into a single interface. The tool is available as open source and targets developers working across frameworks such as .NET, C++, Electron, and Rust.
The announcement reflects long-standing complexity in Windows development. Building modern Windows applications often requires coordinating multiple SDKs, editing manifests, generating certificates, and handling packaging requirements. This fragmentation is particularly visible for developers working outside Visual Studio or MSBuild-based workflows, where integrating modern Windows APIs can require significant manual setup. WinApp CLI aims to address this by acting as a unified entry point for environment setup, configuration, and packaging. According to Microsoft, the tool bridges the gap between cross-platform tooling and Windows native capabilities by automating access to both the Windows SDK and the Windows App SDK.
One of the central features is the one-command environment initialisation. The winapp init command downloads required SDKs, generates projections such as C++ WinRT bindings, and creates manifests, assets, and development certificates. This replaces what previously required multiple manual steps and toolchain-specific configuration.
In addition, the CLI introduces a package identity workflow optimised for inner loop development. Many modern Windows APIs, including notifications, shell integration, and AI capabilities, require apps to have a package identity. Traditionally, this meant fully packaging the application. With winapp create-debug-identity, developers can attach an identity to an executable without full MSIX packaging, enabling faster iteration and testing.
The release also includes automation for manifests, certificates, and signing. Commands are available to generate and install development certificates, update manifest assets, and produce signed MSIX packages suitable for distribution. These capabilities are designed to integrate with CI/CD pipelines, with official GitHub Actions and Azure DevOps tasks supporting environment setup via winapp restore.
Another notable addition is targeted support for Electron and Node.js scenarios. Developers can inject package identity directly into a running Electron process using winapp node add-electron-debug-identity, enabling access to APIs that normally require packaged apps. Microsoft has also started exposing experimental Node.js projections for Windows APIs, including AI-related capabilities.
However, the tool is currently in public preview, and Microsoft notes that commands and features may change before general availability. Developers adopting the CLI should expect breaking changes and gaps in documentation or framework support. After the initial January release, an updated version 0.2.0 was released in late February 2026, with bug fixes and additional improvements.
The WinApp CLI is available via WinGet, npm for Electron scenarios, and as a GitHub project where issues and contributions are encouraged. Microsoft is positioning the tool as a complement rather than a replacement for existing IDE-based workflows, particularly for teams using cross-platform stacks.
Further details, installation instructions, and samples are available in the official announcement blog and the GitHub repository.