Development#
Build the app and publish the companion into its output Mcp directory:
dotnet build src\Hotshot.App\Hotshot.App.csproj -c Release -p:Platform=x64
dotnet publish src\Hotshot.Mcp\Hotshot.Mcp.csproj -c Release -r win-x64 --self-contained true -o src\Hotshot.App\bin\x64\Release\net10.0-windows10.0.26100.0\win-x64\Mcp
build\package.ps1 includes the companion and plugin assets for both architectures. CI validates manifest/version consistency and the official MCP client handshake/tool/image contract. The native harness uses generated images and an isolated profile; no private screenshots are sent to an AI provider.
pwsh tests\Hotshot.Agents.Manifests.ps1
dotnet run --project tests\Hotshot.Mcp.Harness\Hotshot.Mcp.Harness.csproj -c Release -- <absolute-path-to-Hotshot.Mcp.exe>
dotnet run --project tests\Hotshot.Agents.Harness\Hotshot.Agents.Harness.csproj -c Release -p:Platform=x64
pwsh tests\Hotshot.App.Smoke.ps1 -Exe <path-to-built-Hotshot.exe> -AgentSettingsOnly
The native harness captures only its own synthetic Win32 window/region and verifies exact pixels, policy, naming, delay and cancellation. The Settings-only smoke changes neither clipboard nor screenshots, temporarily replaces/restores the profile and requires Hotshot to be closed first.