[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
- 平均合并
- 16 小时 38 分钟
- 30 天内合并 PR
- 327
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
getopenscreen/openscreen 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
getopenscreen/openscreen#1423 ·
维护者通常 1 天内回复
-
Native review wanted: machine-translated recording bar tooltips (14 locales)可能重新可做 @auberginewly 于 20 天前认领，目前没有进行中的 PR。 未关闭good first issue help wanted
难度 2/5 1-3 小时 新手友好度 68/100
getopenscreen/openscreen#913 · 5 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 55/100
getopenscreen/openscreen#1431 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 3/5 半天 新手友好度 68/100
getopenscreen/openscreen#1428 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
getopenscreen/openscreen#1426 ·
维护者通常 1 天内回复
查看 getopenscreen/openscreen 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:web p3
难度 2/5 1-3 小时 新手友好度 72/100
Lets-Parley/Parley#912 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
wealthfolio/wealthfolio#2376 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
be-BOP-io-SA/be-BOP#2817 ·
维护者通常 5 天内回复
-
documentation good first issue
难度 1/5 1-3 小时 新手友好度 84/100
sno-ai/sno-station#149 · 1 条评论 ·
维护者通常 1 天内回复