Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Geschlossen
  • Stimmt etwas nicht?
#1 12 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
15/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
macos, swift
Bereich
accessibility, desktop

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Swift
Sterne
0
Forks
0
Ø Merge
39 Min.
Gemergte PRs (30 T.)
144

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus githubnext/desktop-tools

Alle Issues in githubnext/desktop-tools

Ähnliche Issues

Weitere Issues zu Swift

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.