Run the checks no automated test covers, on a real Mac
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
- Domínio
- desktop-dev, testing-qa
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-checkreports 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_insertis 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_writeis still refused until the receiving app quits. (#3) - Paste an image into a plain-text TextEdit document. The result is
unknownwithclipboard_ownership: "reserved", and quitting TextEdit releases the reservation. (#99) - Kill the client during a 5 s
desktop_press, and again during a 5 sdesktop_drag. Both times the button is up within about 7 s, and a later click works. (#45, #2) - Turn on Pause All Input.
desktop_clickanddesktop_clipboard_writeare refused, whiledesktop_windowsanddesktop_inspectstill 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_notificationsreads a banner, anddesktop_notification_actionclose,openand 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_spaceswitches. A window on another Space reportsavailability.reason: other_space, and switching to that Space recovers it. (#66, #1) -
desktop_fullscreenenters full screen, then exits back to a desktop Space. (#78) - Two displays, one left of or above the main one:
desktop_click,desktop_scrollanddesktop_dragon the second display land where intended. Rearranging the displays between inspect and click gets the click refused. (#2) -
desktop_system_keyvolume, mute, play/pause and brightness keys work. (#80) - Slack or VS Code: the first
desktop_inspectturns 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_inspectand onedesktop_typecomplete. (#27)
Unknowns to answer. These aren't pass/fail; write the answer here.
- Numbers and Excel: does
desktop_set_cellfind an editable control in a cell, or refuse withCELL_NOT_EDITABLE? (#92) desktop_closeon a Finder window once returnedunknownalthough 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
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de githubnext/desktop-tools
-
ace documentation
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 79/100
githubnext/desktop-tools#104 ·
Mantenedores costumam responder em até 1 dia
-
Linux support (meta)Aberta
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 25/100
githubnext/desktop-tools#136 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Select text in a PDFAberta
Dificuldade 3/5 1-2 dias Facilidade para iniciantes 52/100
githubnext/desktop-tools#130 ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 25/100
githubnext/desktop-tools#117 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
live-check-only
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 25/100
githubnext/desktop-tools#23 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
Todas as issues de githubnext/desktop-tools
Issues semelhantes
-
Review backlog (style): Test helper still reads stdout after waitUntilExitTalvez já em andamento @hivecommons-hive assumiu hoje. Abertaagent/reviewer help wanted hive/claimed-by-scanner stage/030-pr-in-progress
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
hivecommons/hotshot#243 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
Ctrl+C while pictures are drawing also kills the image worker (traceback, story ends partial/failed)Abertalow-priority
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
jessvb/tiny-talk-adventures#92 ·
Mantenedores costumam responder em até 1 dia
-
good first issue
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 67/100
Mantenedores costumam responder em até 1 dia
-
bug tests
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
jonathanong/no-mistakes#2261 ·
Mantenedores costumam responder em até 1 dia