git404hub

what is windowsautoprofiles fr?

lahcim/windowsautoprofiles — explained in plain English

Analysis updated 2026-05-18

1PowerShellAudience · developerComplexity · 3/5Setup · moderate

tl;dr

A Windows command line tool that installs and switches between app workspace profiles, combining WinGet packages, folders, shortcuts, and settings into one repeatable setup.

vibe map

mindmap
  root((WindowsAutoProfiles))
    What it does
      Install app profiles
      Switch workspaces
      Capture installer state
    Features
      WinGet packages
      Folders and shortcuts
      Environment variables
      Sandbox capture
    Tech Stack
      PowerShell
      WinGet
      Windows Sandbox
    Audience
      Developers
      Windows power users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Set up a full development workspace, including apps, folders, and environment variables, with one install command.

VIBE 2

Share a reusable Windows workspace definition with others through a GitHub profile link.

VIBE 3

Switch between different app and environment setups by activating different profiles.

VIBE 4

Capture the setup state of installers that WinGet cannot fully represent, using Windows Sandbox.

what's the stack?

PowerShellWinGetWindows SandboxMSI

how it stacks up fr

lahcim/windowsautoprofilesc0urag1/break-risk-intel-skilldw-dwain/ai-gen-company-stack
Stars111
LanguagePowerShellPowerShellPowerShell
Setup difficultymoderateeasyeasy
Complexity3/52/52/5
Audiencedeveloperops devopsdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires Windows 10/11, PowerShell 5.1+, and WinGet, Sandbox capture needs Windows Sandbox and admin rights.

No license is stated in the README.

in plain english

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.

prompts (copy fr)

prompt 1
Walk me through installing WAP and running wap init for the first time on Windows.
prompt 2
Show me how to write a WAP profile.yaml that installs WinGet packages and sets up folders and shortcuts.
prompt 3
Explain the difference between wap install, wap profile install, and wap profile activate.
prompt 4
Help me create a WAP profile similar to the electronics example that installs Arduino IDE and KiCad.

Frequently asked questions

what is windowsautoprofiles fr?

A Windows command line tool that installs and switches between app workspace profiles, combining WinGet packages, folders, shortcuts, and settings into one repeatable setup.

What language is windowsautoprofiles written in?

Mainly PowerShell. The stack also includes PowerShell, WinGet, Windows Sandbox.

What license does windowsautoprofiles use?

No license is stated in the README.

How hard is windowsautoprofiles to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is windowsautoprofiles for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.