Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Run the checks no automated test covers, on a real Mac

未關閉
#129 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
42/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
macos, swift

研究方向

Start with npm run live-check, then follow the checklist in issue #129 on the required real-Mac setup; use docs/mcp.md for the Codex check. Run each scenario exactly as written, excluding macOS 27, and record any failed behavior in linked bug issues. Done means every pass/fail box is resolved and the two unknowns are answered.

由索引模型根據 Issue 內容生成。

描述

These checks have never run on a real Mac, and no automated check covers them. Everything else that shipped is covered by npm run live-check, by unit tests, or by agents using the tools every day.

Tick a check when it passes. If one fails, open a bug and link it here. Close this issue when every box is ticked.

  • Automated run: npm run live-check reports PASS for every check.

Safety. If one of these fails, a clipboard is lost or a mouse button stays held down.

  • Kill the MCP client while desktop_insert is pasting into TextEdit. Afterwards the clipboard holds either the original contents, or the inserted text with the reservation held. Older contents are never restored over a newer copy. (#3)
  • Quit Desktop Tools right after an insert that returned unknown, then relaunch it. desktop_clipboard_write is still refused until the receiving app quits. (#3)
  • Paste an image into a plain-text TextEdit document. The result is unknown with clipboard_ownership: "reserved", and quitting TextEdit releases the reservation. (#99)
  • Kill the client during a 5 s desktop_press, and again during a 5 s desktop_drag. Both times the button is up within about 7 s, and a later click works. (#45, githubnext/desktop-tools#2)
  • Turn on Pause All Input. desktop_click and desktop_clipboard_write are refused, while desktop_windows and desktop_inspect still work. Resuming lets the same click through, and a relaunch starts unpaused. (#100)

Never run on macOS 27. These were built from documentation or from how older macOS versions behave.

  • Notifications: desktop_notifications reads a banner, and desktop_notification_action close, open and an app action (Reminders "Mark as Completed") each do what they say. If they don't, record the banner's AX roles and action names. (#74)
  • Spaces: desktop_switch_space switches. A window on another Space reports availability.reason: other_space, and switching to that Space recovers it. (#66, githubnext/desktop-tools#1)
  • desktop_fullscreen enters full screen, then exits back to a desktop Space. (#78)
  • Two displays, one left of or above the main one: desktop_click, desktop_scroll and desktop_drag on the second display land where intended. Rearranging the displays between inspect and click gets the click refused. (#2)
  • desktop_system_key volume, mute, play/pause and brightness keys work. (#80)
  • Slack or VS Code: the first desktop_inspect turns on web accessibility and lists the app's web fields, and the window still moves and resizes normally. (#107)
  • Approved Agents: a new agent's first action shows the prompt. Allow lets it through, and Revoke and Forget work from the menu. (#120)
  • Codex: with the [mcp_servers.desktop] entry from docs/mcp.md, desktop_apps, desktop_inspect and one desktop_type complete. (#27)

Unknowns to answer. These aren't pass/fail; write the answer here.

  • Numbers and Excel: does desktop_set_cell find an editable control in a cell, or refuse with CELL_NOT_EDITABLE? (#92)
  • desktop_close on a Finder window once returned unknown although the window closed. Does that still happen? Answered: Accessibility lists Finder's desktop as a window without an ID, which made every Finder close unverifiable on macOS 27. Fixed in 0.14.1 (#133).

The focus bug (#23) and background paste into web apps (#5) have their own issues.

主要語言
Swift
星號
0
分支
0
平均合併
39 分鐘
30 天內合併 PR
144

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

githubnext/desktop-tools 的其他 Issue

查看 githubnext/desktop-tools 的全部 Issue

相似的 Issue

更多 Swift Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。