Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#129 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
42/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
macos, swift
領域
desktop-dev, testing-qa

調査の方向性

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, #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, #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? (#4)

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

主要言語
Swift
スター
0
フォーク
0
平均マージ
19分
マージ済み PR（30日）
107

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

githubnext/desktop-tools のほかの issue

githubnext/desktop-tools の issue をすべて見る

似ている issue

Swift の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。