[Feature]: Let an MCP client or script know when a recording finishes
維護者通常 1 天內回覆
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 22/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- ai-infra-agents, electron, typescript
研究方向
Start with the in-app MCP server and its existing tools, startRecording and stopRecording, to see how a take's end and the new project's projectId are exposed today. The issue offers two designs, a settings-driven command hook or an MCP notification or waitForRecording tool, so a maintainer needs to choose one before coding. Done means a client receives the new project's id and path once a take is saved and opened in the editor.
由索引模型根據 Issue 內容生成。
描述
Search existing issues
- I have searched the existing issues
Is your feature request related to a problem?
I edit demo recordings with Claude Code through the in-app MCP server (trims, zooms, labels). Nothing tells the agent that a take has ended, so I start it by hand. My workaround is to watch the projects folder for a new proj_*.openscreen file. That depends on the storage layout, which on the Windows Store install sits under Packages\...\LocalCache. It also can't tell a finished recording from an imported project.
Describe the solution you'd like
Either of these would work:
- A setting under AI settings, "After a recording, run:", with a command that receives the new project's id and path.
- An MCP notification to connected clients when a take is saved and opened in the editor, carrying the
projectId. Or a tool such aswaitForRecordingthat returns once the user stops a take from the recording bar.
Describe alternatives you've considered
- Watching the projects folder, as above.
- Having the agent drive
startRecording/stopRecordingitself. That works, but it takes the Record button away from the person recording.
Additional context
OpenScreen 2.0.0 (Microsoft Store package), Windows 11, in-app MCP server with MCP edits on. Related to #1180, but this asks for an event rather than tool coverage.
Drafted with Claude Code; reviewed by me.
- 主要語言
- TypeScript
- 星號
- 3.7k
- 分支
- 231
- 平均合併
- 17 小時 7 分鐘
- 30 天內合併 PR
- 277
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
getopenscreen/openscreen 的其他 Issue
-
Native review wanted: machine-translated recording bar tooltips (14 locales)可能重新可做 @auberginewly 於 27 天前認領，目前沒有進行中的 PR。 未關閉good first issue help wanted
難度 2/5 1-3 小時 新手友好度 68/100
getopenscreen/openscreen#913 · 5 則留言 ·
維護者通常 1 天內回覆
-
enhancement
難度 4/5 3-5 天 新手友好度 48/100
getopenscreen/openscreen#1483 ·
維護者通常 1 天內回覆
-
enhancement
難度 4/5 3-5 天 新手友好度 42/100
getopenscreen/openscreen#1477 ·
維護者通常 1 天內回覆
-
bug
難度 4/5 3-5 天 新手友好度 48/100
getopenscreen/openscreen#1475 · 4 則留言 ·
維護者通常 1 天內回覆
-
enhancement
難度 4/5 3-5 天 新手友好度 35/100
getopenscreen/openscreen#1473 ·
維護者通常 1 天內回覆
查看 getopenscreen/openscreen 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 83/100
appandflow/stim#5258 ·
維護者通常 1 天內回覆
-
area/docs framework/hugo help wanted language/markdown
難度 1/5 1 小時以內 新手友好度 88/100
維護者通常 1 天內回覆
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
難度 1/5 1 小時以內 新手友好度 68/100
lingdojo/kana-dojo#33660 · 1 則留言 · 5 個 reaction ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
drizzle-team/drizzle-orm#6639 ·
維護者通常 4 天內回覆
-
enhancement
難度 2/5 1-3 小時 新手友好度 76/100