Skip to content

Computer use: OCR/pictureOnly fallback and Windows (UIAutomation) backend #123

Closed

Description

@Tryanks

Status — DONE (2026-08-25)

The Windows track is implemented and validated on real hardware; nothing tracked here remains except an optional CDP-roots nicety noted below.

Shipped:

outline/state/tool-surface stay platform-neutral, so improvements apply across every provider.

Deliberately not done (out of scope, low value):

  • CDP browser roots — enumerating Chromium DevTools targets as observation roots. A documented v1 deviation; open a fresh issue if it's ever wanted.
  • Linux AT-SPI backend — no demand; add if it appears.

Closing: the accessibility-tree gap this issue was filed for (macOS-only, no OCR/pictureOnly path) is closed on both counts — Windows has a real UIA backend, and text-sparse windows fall back to raw images.

Activity

  1. Tryanks commented on Aug 24, 2026

    @Tryanks
    OwnerAuthor

    Windows UIAutomation backend implemented (PR #268, over the uiautomation crate) and validated on physical Windows 11 — real multi-node UIA trees, root enumeration, and text-sparse classification all confirmed. Combined with the raw-image fallback (#258), the accessibility gap this issue tracked is closed. CDP roots / Linux AT-SPI left as optional future work per the body.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions