Files
qwen-code/packages/cua-driver/docs/linux-desktop-validation.md
T
顾盼 a791e47a54 feat(cua): streamline computer use and port native reliability fixes (#14846)
* feat(cua): preload the JavaScript computer use runtime

* refactor(cua): remove the native Wayland backend

* feat(cua): move app computer use into the driver

* feat(cua): preserve background delivery and port platform fixes

* feat(cua): add explicit desktop input and browser runtime facade

* feat(cua): package the unified 0.26.0 computer use runtime

* fix(cua): finalize cross-platform native reliability

* fix(cua): isolate runtime releases from CLI versioning

* fix(cua): keep Electron out of root workspace installs

* fix(cua): synchronize consumers and async cleanup tests

* fix(browser): migrate smoke to preloaded cua runtime

* docs(cua): document MCP setup for Qwen Code Claude Code and Codex
2026-10-21 14:03:31 +08:00

1.9 KiB

Linux representative desktop validation

Hosted CI owns the canonical Xvfb/Openbox environment. Some contracts require a real user desktop and therefore run only when a maintainer explicitly provisions the corresponding environment.

Environments

Environment Required evidence Current status Preflight
Real Xorg MPX/uinput behavior that Xvfb cannot provide Not yet validated Xorg session with /dev/uinput access

Source ownership

The host checkout is the only checkout that commits or pushes. Sync it with:

packages/cua-driver/scripts/sync-vm-worktree.sh push user@host '~/cua'

The sync writes .cua-e2e-source-sha after transferring the worktree. The canonical preflight validates that marker when the VM intentionally has no .git directory, so reports still identify the exact host commit.

Run

Start the command from the graphical user's systemd user manager or an equivalent terminal inside that user's session. The wrapper rejects the wrong desktop generation before building fixtures.

scripts/ci/linux/run-rust-e2e-desktop.sh xorg

The default is the complete canonical matrix. CUA_E2E_INTERNAL_LANE and CUA_E2E_HARNESS_FILTER remain diagnostic/maintainer controls; they do not define a second catalog.

Evidence acceptance

Behavioral acceptance requires typed rows, the exact source SHA, independent fixture-state or refusal evidence, and every action-specific desktop oracle. A representative result without reporter-owned per-cell video may establish that behavior, but it is recorded as lacking full evidence parity.

Full hosted parity also requires the Markdown summary, screenshots, trajectories, and per-cell videos enforced by the reporter. Record accepted behavior and any evidence-parity gap in action-support.md. A setup failure is an environment error, never a smaller green matrix.