wtf is windowsautoprofiles?

WindowsAutoProfiles, called WAP for short, is a command line tool for Windows that installs and switches between named app profiles. A profile is a description of a workspace: which WinGet packages to install, which folders, shortcuts, environment variables, and PATH entries it needs, and optionally captured setup data from Windows Sandbox for installers that WinGet cannot fully handle on its own. The project describes itself as more than a WinGet wrapper with named profiles. WinGet only installs apps, while WAP turns a group of apps into a repeatable workspace by combining the installed packages with folders, shortcuts, environment variables, and recorded configuration state. The author's stated long term goal is something like Docker Compose, but for Windows desktop environments, where installing one workspace could set up an entire toolchain such as an electronics workspace with an IDE, shared libraries, project templates, editor extensions, and terminal settings all at once. After installing WAP with its MSI installer, you run one command to initialize it, then either install a profile directly from a GitHub URL, or download it first so you can review or edit it locally before installing and activating it. Profiles can also be refreshed if they change. The README lists commands for initializing, installing, activating, deactivating, and uninstalling profiles, for adding WinGet packages to a profile, and for starting or removing a Windows Sandbox capture. Installing a profile creates workspace folders, installs the packages it lists, creates shortcuts, and records what WAP owns so it can be cleanly removed later. Activating a profile applies its environment variables and PATH entries, and deactivating reverses only those changes. Uninstalling removes WAP owned installs and shortcuts but keeps your workspace data unless you explicitly ask it to clean up. The repository ships two example profiles, one for general developer tools and one for electronics work with Arduino IDE and KiCad. WAP requires Windows 10 or 11, PowerShell 5.1 or newer, WinGet for package installs, and Windows Sandbox if you want to use its capture feature. It is written in PowerShell and its documentation covers installation, everyday usage, the full command reference, and the profile file format.