Repository navigation
Inspect Chrome windows with Accessibility when the page title changes #6
Description
While smoke-testing a timeline fix in channel streaming-message-overlap, desktop_inspect in accessibility mode failed repeatedly on a Google Chrome window (window 474, title "Ace") that pixels mode captured fine:
DESKTOP_ERROR: The desktop observation provider returned inconsistent response evidence: window-context window title..
At the time (before githubnext/ace#156), without an action snapshot the agent could not click into the app, so the smoke test moved to a Playwright-driven Chrome for Testing outside Ace's tools.
Status (Oct 6)
The Accessibility-mode title mismatch is not fixed; it reproduced again on Oct 6 (details). githubnext/ace#156 mitigates it for pointer input: pixel inspection now returns a single-use snapshot that authorizes exact-window point clicks, scrolls and drags. Element-based actions, text selection and insertion still need a working Accessibility snapshot.
Part of githubnext/ace2#8.
Activity
iamnbutler commentedon Oct 6, 2026
Reproduced while smoke-checking githubnext/ace#149 in Google Chrome PID 62587, window 8673 (a standalone Ace window at the isolated source host on port 4342). Two accessibility inspections returned inconsistent response evidence: window-context window title. Pixel inspection succeeded and showed the loaded app, but could not provide action authority. No input was dispatched.
iamnbutler commentedon Oct 13, 2026
The native desktop engine moved to githubnext/desktop-tools in githubnext/ace#213. This is engine work, so it's being transferred there in the pre-Universe cleanup. Ace-side tool schemas, the channel desktop gate, and hosted forwarding stay in ace2.
iamnbutler commentedon Oct 15, 2026
Repro from the Ace desktop tools study (githubnext/ace#427), D7 on Canary 0.0.46+8fbfcc3. Google Chrome, window 142, showing a local page whose title was static, "Compose fixture". The query that would have made it tick was dropped; see #20.
desktop_inspectin accessibility mode failed twice withDESKTOP_ERROR: The desktop observation provider returned inconsistent response evidence: window-context window title..The title wasn't changing, so this is the Accessibility title vs window-server title mismatch itself, not a race.mode: "pixels"worked. The agent then stopped without filling the field: it had no elements, and it didn't try coordinate clicks as it had in Safari. Chrome pages can't be operated today unless the agent falls back to pixels on its own.