Repository navigation
build(store): add an openscreen execution alias to the MSIX - #1311
Conversation
The Store package lives in a versioned folder under WindowsApps, so an agent or a script had no path to register for the CLI or for openscreen mcp. The alias puts openscreen.exe in %LOCALAPPDATA%\Microsoft\WindowsApps, which is on the PATH. An alias needs a MinVersion of 16299; it moves to 18362, the 1903 the app already requires. Checked on a test package registered from the installed 2.1.0: openscreen help exits 0 and openscreen mcp lists its 55 tools through the alias.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Summary
The Microsoft Store package lives in a versioned folder under
WindowsApps, so an agent or a script had no stable path to register for the CLI oropenscreen mcp. The MSIX now declares an app execution alias,openscreen.exe, which Windows puts in%LOCALAPPDATA%\Microsoft\WindowsApps, already on the PATH.build/appx-extensions.xmlholds theuap5:AppExecutionAliasextension, wired throughappx.customExtensionsPath.appx.minVersionmoves to10.0.18362.0: an alias needs 16299, and the app already requires 1903. Side effect:MaxVersionTestedfollows it, from electron-builder's default 14316 to 18362.Once this ships,
website/docs/cli.md(Microsoft Store row) and its translations can sayopenscreen. The demo skill already handles both cases.Test plan
electron-builder --win appx --prepackaged). MakeAppx accepts the manifest.openscreen.exeappears inWindowsApps.openscreen helpexits 0 through the alias.openscreen mcpanswersinitialize(server 2.1.0-rc.6) and lists 55 tools,startRecordingincluded.🤖 Generated with Claude Code
Summary by CodeRabbit
openscreen.execommand.