Argument errors in system_key and desktop_wait that agents trip on
維護者通常 1 天內回覆
已經有一個關聯 PR 被合併了。
- #220 來自 @iamnbutler —— 已合併
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 55/100
- Issue 類型
- 功能
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- macos, swift
- 領域
- desktop-dev
研究方向
Start with the MCP tool schemas and implementations for desktop_system_key and desktop_wait, then trace click handling and post-click observation timing. Validate that return aliases enter, responses identify the frontmost app, and the wait schema documents required fields and timeout bounds. Done means calls succeed on the first attempt with accurate feedback, and observation does not report a click as unchanged before its effect is visible.
由索引模型根據 Issue 內容生成。
描述
Seen 2026-10-23 with Desktop Tools 0.17.1 (app and MCP), driving Ace Canary on macOS 27. Ace is an Electrobun app, so its UI is a WKWebView. The agent was a foreground Claude Code session recording demo videos.
Small schema issues that each cost a failed call:
desktop_system_keywithreturnfails with "Choose a named key or one printable character."enterworks. Acceptreturnas an alias, since it's the key's name on a Mac.- Every
desktop_system_keycall comes back as unknown: "The keys went to whatever was frontmost; their effect was not read back." That's fair for the route, but it should say which app was frontmost when the keys were sent. desktop_waitwithelement_appearsneeds both role and title, andelement_goneneeds element. The schema doesn't say so.timeout_msmust be an integer from 100 to 45000. List those constraints in the tool description so the first call is right.- An element click on Ace's New channel button returned completed while the next observation looked unchanged, yet the channel had been created. The observation after a click may be read too early.
- 主要語言
- Swift
- 星號
- 0
- 分支
- 0
- 平均合併
- 39 分鐘
- 30 天內合併 PR
- 162
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
githubnext/desktop-tools 的其他 Issue
-
Accessibility inspect returns far-offscreen elements, blowing the budget on long pages可能已有人在做 @iamnbutler 於 3 天前認領。 未關閉
難度 4/5 3-5 天 新手友好度 48/100
githubnext/desktop-tools#178 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 15/100
githubnext/desktop-tools#143 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 4/5 3-5 天 新手友好度 42/100
githubnext/desktop-tools#129 ·
維護者通常 1 天內回覆
-
enhancement
難度 5/5 一週以上 新手友好度 8/100
githubnext/desktop-tools#5 · 11 則留言 ·
維護者通常 1 天內回覆
查看 githubnext/desktop-tools 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 71/100
Cocoanetics/Loupe#8 ·
-
[Pri] Low [Status] Ready for Dev [Type] Bug Blogging Prompts Notifications
難度 2/5 1-3 小時 新手友好度 79/100
wordpress-mobile/WordPress-iOS#26256 · 1 則留言 ·
維護者通常 1 天內回覆
-
copy design-review mac P3
難度 2/5 1-3 小時 新手友好度 88/100
tosunlab/hisarapp-core#510 ·