Validate desktop tool use in Ace and track known gaps
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 8/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- macos, typescript
- 领域
- desktop-dev, testing
调研方向
This is a tracking issue for validating desktop tools in a signed Canary, not a single change. The one open check is the sharing path: a teammate's invocation with sharing on should reach desktop tools as the owner allowed, and with sharing off it should be refused. The upstream engine and its gaps live in githubnext/desktop-tools, so start with native/patches/README.md there for the Peekaboo patch state. Done means every check passes in a Canary with a real provider run and each gap is fixed or accepted.
由索引模型根据 Issue 内容生成。
描述
Validate the desktop tools as Ace ships them, and keep the known gaps in one place. The engine and its roadmap live in githubnext/desktop-tools (the former meta is githubnext/desktop-tools#11). This issue covers only what Ace owns: the pinned package, the channel setting, sharing, and the agent's experience in real runs.
Done when: every check below has passed in a signed Canary with a real provider run, with that Canary's version noted, and every gap is fixed or explicitly accepted.
Validation
- An agent drives TextEdit, then screenshots and reads its window. The screenshots stream to a teammate. (Study scenario 20, 0.0.36.)
- The agent fills a Save sheet's name, picks a folder and saves (#378 via githubnext/ace#382 and desktop-tools#8, 20b, 0.0.38).
-
desktop_inserttypes into a Save sheet's filename field (#390 via githubnext/ace#402 and desktop-tools#9, 20c). - Turning desktop tools off refuses every
desktop_*call. The refusal is clear, and turning them back on works without restarting the channel. (Study D2, 0.0.46.50.) - A teammate's invocation with sharing on reaches desktop tools as the owner allowed. With sharing off it is refused. The sharing text matches what happens.
- Stopping a run, or losing the connection, during a desktop action settles it as completed, refused or unknown, and the action isn't replayed after the worker reopens. (Study D3b/D3c, 0.0.46.50.)
- Two channels with desktop tools on at the same time don't act on each other's targets. (Study D4 and R1, 0.0.46.51 and .52. Agents can't yet tell whose new window is whose: githubnext/desktop-tools#17.)
- Peekaboo patch tests pass at the pinned commit (desktop-tools#10, Ace githubnext/ace#425). Every pin bump re-runs them. (8801b31 in full; 4618b33 adds one bridge patch, and its bridge tests pass.)
Known gaps
- Shell capture: with desktop tools off, the shell can still capture the screen with Ace's macOS permissions. Isolating that is not planned (#379). The wording in githubnext/ace#380 and githubnext/ace#389 documents it.
- Background key presses:
desktop_keycan't verify a background Cmd+W. The recovery hint suggests--foreground, which the tool doesn't expose (githubnext/desktop-tools#11, comment from October 7). - Engine gaps, tracked in desktop-tools:
- focus and paste in WebKit (githubnext/desktop-tools#5);
- temporary clipboard paste (githubnext/desktop-tools#3);
- pointer delivery and multiple displays (githubnext/desktop-tools#2);
- Chrome's Accessibility titles (githubnext/desktop-tools#6);
- why inspection is unavailable (githubnext/desktop-tools#1);
- window, menu and dialog workflows, including Ace's own Open Folder picker (githubnext/ace#531);
- patch drift in dev builds (githubnext/desktop-tools#7).
- Not available everywhere: cloud compute channels have no desktop, so their toggle is hidden (#422). Hosted channels use the workspace host's desktop. Operating a teammate's desktop is deferred (#202).
- Upstream test failures: two Peekaboo tests fail on unpatched 4.8.0 as well (
native/patches/README.mdin desktop-tools).
Tracked by githubnext/ace#5.
- 主要语言
- TypeScript
- 星标
- 1
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
githubnext/ace2 的其他 Issue
-
documentation
难度 2/5 1-3 小时 新手友好度 76/100
githubnext/ace2#530 · 1 条评论 ·
-
难度 1/5 1 小时以内 新手友好度 88/100
githubnext/ace2#437 ·
-
难度 4/5 3-5 天 新手友好度 35/100
githubnext/ace2#529 ·
-
难度 4/5 3-5 天 新手友好度 45/100
githubnext/ace2#528 ·
-
难度 5/5 一周以上 新手友好度 20/100
githubnext/ace2#511 ·
相似的 Issue
-
area:editor bug issue-form:bug P0 platform:windows review: low
难度 2/5 1-3 小时 新手友好度 64/100
1lck/Lithe-IDEA#1388 ·
维护者通常 1 天内回复
-
fix(api): isToolAuditEnabled swallows database read errors on auditToolOperations without logging未关闭area: backend bug priority: low
难度 2/5 1-3 小时 新手友好度 82/100
snapotter-hq/SnapOtter#3238 ·
维护者通常 1 天内回复
-
rig up --plan times out after 5 s and reports an UNKNOWN outcome while the daemon completes the plan未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
modelcontextprotocol/servers#5216 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复