windows-build
Skill39 starsChanged 4 months agoMITView on GitHub
Build, run, or debug the Windows side of Consult User MCP (dialog-cli-windows WPF CLI, windows-app tray app, Velopack installer) over SSH to the Windows machine. Use when asked to build/test/fix anything Windows in this project, when a change touches dialog-cli-windows/ or windows-app/, or when the Windows installer needs rebuilding.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- bcgit/bc-javatheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- bcgit/bc-java★ 2.7ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- container/CLAUDE.mdCLAUDE.md
- dialog-cli/CLAUDE.mdCLAUDE.md
- dialog-cli-windows/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- macos-app/CLAUDE.mdCLAUDE.md
- mcp-server/CLAUDE.mdCLAUDE.md
- sketch-cli/CLAUDE.mdCLAUDE.md
- test-cases/CLAUDE.mdCLAUDE.md
- windows-app/CLAUDE.mdCLAUDE.md
- beadsSkill
- release-appSkill
The file
Files
Windows builds
Nothing Windows can be built or tested from macOS. .NET/WPF and Velopack need the real environment.
ssh user@192.168.178.197Repo: C:\Users\jurre\PycharmProjects\consult-user-mcp
Commands run through cmd.exe by default. For PowerShell use powershell -Command "..." or powershell -ExecutionPolicy Bypass -File ....
Prerequisites on that machine
dotnet SDK 8.0 · node/npm · gh CLI (authenticated) · vpk (dotnet tool install -g vpk)
Builds
cd dialog-cli-windows && dotnet publish -r win-x64 --self-contained -p:PublishSingleFile=true
cd windows-app && dotnet build # dev
cd windows-app && dotnet publish -c Release -r win-x64 --self-contained
powershell -ExecutionPolicy Bypass -File scripts\build-windows-installer.ps1Gotchas
- stderr aborts the installer script.
build-windows-installer.ps1sets$ErrorActionPreference = "Stop", so a Node.jsExperimentalWarningon stderr kills the build. The script flips it toContinuearound npm/npx calls — wrap any new npm command the same way. dialog-cli-windows/cannot be renamed todialog-cli/. It would collide with the macOS Swift CLI directory.%APPDATA%\ConsultUserMCPcannot be renamed. Existing users' settings and snooze state live there.- Velopack + WPF setup is unusual.
App.xamlis aPage, not anApplicationDefinition; the entry point is a customMainwithStartupObjectset in the csproj. Do not "fix" this back to the WPF default. <UseWPF>true</UseWPF>and anet8.0-windowstarget are both required.System.Drawingneeds an explicitSystem.Drawing.CommonNuGet reference on .NET 8.
Parity
The Windows dialog CLI must accept the same JSON and print the same response shape as the macOS one — mcp-server calls both through one DialogProvider interface. See .claude/rules/dialog-parity.md.
tweak and propose_layout are macOS-only; WindowsDialogProvider throws for both. That is intentional, not a bug to fix incidentally.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

