Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#1 12 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
15/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
macos, swift
Área
accessibility, desktop

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Swift
Estrellas
0
Forks
0
Merge medio
15 min
PR fusionados (30 d)
94

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de githubnext/desktop-tools

Todos los issues de githubnext/desktop-tools

Issues similares

Más issues de Swift

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.