Skip to content

Validate Cua desktop access across Pylon providers and setup lifecycles #537

Description

@rynfar

Cua desktop access and guided driver management are implemented in #525. Track remaining live validation here while making the optional integration available. Keep this issue open after the implementation merges.

Already verified: all code CI checks on c5cae20 are green; 61 focused computer tests and 5 setup UI tests pass; independent adversarial review found no remaining concrete blockers. A real macOS background click, screenshot, and state assertion succeeded without changing the foreground app or pointer. Official macOS/Linux/Windows archives extract successfully, and the macOS bundle passes publisher verification. Settings detect Driver 0.28.1 and granted permissions. These results do not establish live behavior through every provider/model.

Provider workflows

For each provider, use a real Pylon session to discover tools, capture and interpret a native screenshot, perform a background click and text input, verify resulting state, and confirm tool results and errors render correctly. Record provider/harness/model versions, Pylon commit/build, OS, Driver version, target environment, evidence, and limitations (including models without image support).

  • Codex
  • Claude
  • Cursor
  • Grok
  • OpenCode
  • Antigravity
  • Prime Agent

Setup and environment validation

Use disposable hosts/state for installation mutations and failure scenarios; automated fixture coverage already exists.

  • Packaged desktop: discover Computer settings and complete first-time setup from a build containing Add shared Cua desktop access and guided driver management #525.
  • Fresh install, update, repair, cancellation before activation, and reconnect during setup.
  • Fresh macOS permission denial, grant, timeout, and retry flows.
  • Local, remote, and tunnel sessions target the selected environment server; verify revocation and foreground opt-in boundaries.
  • Live Linux desktop workflows; archive and packaged smoke checks alone do not verify GUI support.
  • Live Windows desktop workflows; archive and packaged smoke checks alone do not verify GUI support.
  • Shared daemon restart with multiple environments/connections, active-action coordination, and documented recovery from a crashed installer lock.
  • Verify and document concurrent-agent/same-application limits and application-specific background behavior.

Agents share the actual target desktop; this does not provide an isolated desktop or VM. Mobile agents receive shared tools, while guided setup currently lives in web/desktop. Do not assume macOS background behavior transfers to other platforms.

Close when results and evidence are recorded for every item, with unsupported combinations explicitly documented and actionable failures linked to follow-up bugs. This issue tracks live validation, not an assertion that every combination is already supported.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions