Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
#129 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
42/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
macos, swift

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Swift
Estrelas
0
Forks
0
Merge médio
19min
PRs com merge (30d)
107

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de githubnext/desktop-tools

Todas as issues de githubnext/desktop-tools

Issues semelhantes

Mais issues de Swift

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.