You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d8bf2d8
Browse filesBrowse the repository at this point in the historyBrowse files
fix(plugin): find a Store install and hand over when the MCP tools are missing
On Windows the openscreen-demo skill told a ChatGPT agent that OpenScreen was
not installed, though the Store build was: the skill claimed an execution alias
that no released Store package ships yet (it lands after 2.1.2). It now points
at the versioned path from Get-AppxPackage, verified as a working stdio server,
and warns against a PowerShell launcher, which drops the server's input after
the first message.
It also says what to do when the tools are missing right after the plugin or
server is added (hand over to a new session), and never to drive OpenScreen's
window with computer use instead.
Copy file name to clipboardExpand all lines: plugin/skills/openscreen-demo/SKILL.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,11 +18,11 @@ You need the tools `startRecording`, `stopRecording`, `exportVideo` and `getFram
18
18
19
19
| OS | Executable |
20
20
|---|---|
21
-
| Windows |`%LOCALAPPDATA%\Programs\Openscreen\Openscreen.exe`, or `C:\Program Files\Openscreen\Openscreen.exe`. The Microsoft Store version is `openscreen` on the PATH from the release after 2.1.0 (`where openscreen`). An older Store version has no fixed path to register: if it is the only one installed, offer the installer below|
21
+
| Windows |`%LOCALAPPDATA%\Programs\Openscreen\Openscreen.exe`, or `C:\Program Files\Openscreen\Openscreen.exe`. The Microsoft Store version: `openscreen` on the PATH once its release ships the execution alias (`where openscreen`); before that, `app\Openscreen.exe` under `(Get-AppxPackage EtienneLescot.OpenScreen).InstallLocation` (in PowerShell). That path carries the version: register it again after a Store update. Never wrap it in a `powershell -Command` launcher: PowerShell swallows the server's input after the first message|
| Linux |`openscreen` on the PATH, or the AppImage |
24
24
25
-
Run `"<executable>" help`: it must list `mcp`. If the app is missing, or too old to list it, offer to install the latest release, and do it only once the user agrees:
25
+
Check every location in the table before you call OpenScreen missing: the Store version is the one most often overlooked. Run `"<executable>" help`: it must list `mcp`. If the app is missing, or too old to list it, offer to install the latest release, and do it only once the user agrees:
26
26
27
27
1. Find the installer for this machine in the latest release of `getopenscreen/openscreen`: `gh release view --repo getopenscreen/openscreen --json assets`, or https://github.com/getopenscreen/openscreen/releases/latest.
28
28
-**macOS:**`Openscreen-macOS-Apple-Silicon-<version>.dmg`, or `-Intel-` (check `uname -m`). Mount it, copy `Openscreen.app` to `/Applications`, unmount it.
@@ -42,6 +42,8 @@ Run `"<executable>" help`: it must list `mcp`. If the app is missing, or too old
42
42
43
43
**Hand over to the next session.** Write the user's request, and anything already decided, to `openscreen-demo-plan.md` in the working directory. Then ask the user to start a new session and say *continue the OpenScreen demo*. In that session, read the file and carry on from step 2.
44
44
45
+
The tools are missing right after the plugin or the server is added: an agent loads its MCP servers when a session starts. Say so in plain words and hand over as above, with the storyboard in the file if you have made one. Never stand in for the missing tools by driving OpenScreen's window with computer use or a mouse tool: it takes over the user's mouse and screen while they may be working.
46
+
45
47
## 2. Plan before recording
46
48
47
49
Write a storyboard and show it to the user in a few lines, then carry on unless they object.
0 commit comments