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

Explain native inspection failure when the desktop or target window becomes unavailable

Fechada
  • Algo errado?
#1 12 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
15/100
Tipo de issue
Bug
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
macos, swift
Domínio
accessibility, desktop

Direção de pesquisa

The payload names no source files. Start from the inventory fields observation_capability, observation_reason, and is_on_screen, and from the typed target_unavailable refusal shipped in #87. Reproduce the offscreen-versus-locked-desktop distinction on macOS, then add the recovery check that githubnext/ace2#8 requires. Done means that check passes and the unavailable-desktop limitation can be removed.

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

Descrição

live-check-only

Status (Oct 6)

Shipped: pixels-mode inspection and target availability reporting (#71), and typed target_unavailable refusal for a known locked session with unlock-and-refresh guidance (#87, details). Remaining: a reliable distinction and recovery path for an offscreen/other-desktop target versus an unavailable desktop versus incomplete Accessibility, sparse initial WKWebView Accessibility trees (seen in #73), and the real recovery check below. The Chrome window-title mismatch is tracked separately in githubnext/desktop-tools#6.

Original report

During real desktop-action dogfooding for githubnext/ace2#8 / githubnext/ace2#63, native inspection became unavailable after previously passing against the same live Ace-dev process and window. The agent received an incomplete Accessibility-tree error without an actionable explanation of target availability.

Observed on the signed macOS development app:

  • The real local pi click/type/key/button workflow and delivered-input Stop/restart checks had passed.
  • A subsequent local Workers/Durable Objects run passed its seed native inspection, then two model desktop_inspect calls failed with DESKTOP_ERROR: Warning: AX tree incomplete at incomplete accessibility read.
  • Fresh native inventory still returned the same process instance/window and bounds, with is_minimized: false, but is_on_screen: false, observation_capability: pixels_only, and observation_reason: no_matching_accessibility_window. Inventory itself reported complete.
  • Codex computer use could still read and capture that test window. Its Raise and Ace's Show Ace action did not restore native availability in the subsequent inventory.
  • No mutation ran in the failed hosted workflow. No evidence establishes whether a Space/desktop/controlled-surface change or another macOS condition caused the availability change; this is not yet a confirmed hosted-transport defect.

Expected: give the agent a bounded, useful explanation when native window/Accessibility availability changes, retain the exact target, and require a fresh observation when the target is available again. Do not silently switch to another window, steal focus, or replay uncertain input as recovery.

Investigate which native state reliably distinguishes an offscreen/other-desktop target, a locked/unavailable desktop, and incomplete Accessibility. Add a real recovery check under githubnext/ace2#8's visual targeting and longer-workflow slice. Keep the unavailable-desktop limitation explicit until that check passes.

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

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.