cua-driver 2.0.1

Verified OpenAgent standard package from 736fc8e.

Cua Driver 2.0.0

Desktop control now uses the standard Agent Plugin MCP contract.

• Root mcp.json declares the embedded stdio desktop server; plugin installation, permissions and MCP lifecycle use shared controls.
• Removes the socket-daemon requirement and standalone CUA application launch. Existing driver caches and screenshot data are retained.
• Bundled Windows browser guidance avoids combining an explicit browser path with URLs, which upstream opens separately through the default browser. Browser preparation refusals must not trigger killing and relaunching the browser.

桌面控制统一使用标准插件 MCP：共享安装、授权和生命周期管理，无需独立 CUA 应用或 socket 守护。保留驱动缓存与截图数据，并补充 Windows 浏览器启动规则，避免指定 Edge 时又通过默认浏览器打开 Chrome。

Validation: 64 package tests, Plugin Kit validation, extracted-archive launcher startup, and native desktop-control qualification of the standard MCP implementation. The browser correction updates agent guidance; it does not patch the upstream driver.

Plugin protocol: 1–1
Source: 28d2806
Archive SHA-256: 24e2576e5c300657b6b0604aaacc811273edbd5f76914f6267b256c60c90342d

cua-driver 1.3.1

Verified OpenAgent standard package from 700d115.

Cua Driver v1.3.0

Cua Driver now automatically checks and installs verified upstream driver updates during startup preparation.

• Checks stable component tags at most once every six hours, including failed attempts.
• Requires the expected platform asset URL and GitHub SHA-256 digest; stages and verifies archives before activation.
• Keeps the last verified driver on update failure, with the built-in pin as a fallback.
• Serializes concurrent preparation and retains old driver directories used by running processes.
• Serve, MCP and stop reuse the selected driver without update checks. A running daemon adopts updates on its next host-supervised start.
• Preserves OPENAGENT_CUA_DRIVER_BIN overrides and desktop authorization, with English and Chinese notices.

启动准备阶段自动检查并安装经过 SHA-256 校验的 CUA 驱动新版；更新失败继续使用已验证版本。正在运行的进程在下次启动时采用新版。

Validation: 55 package tests; full OpenAgent preflight (1008 tests, type checks, production build and bundle budgets); native Windows driver 0.34.0 startup, 59 MCP tools and bounded stop.

Source: 9788a01
SHA-256 (openagent-cua-driver-v1.3.0.tar.gz): a9c8752113138ef189e25e5641ba310c94a97ee5ad064e26e915b5b733e1b2f7

cua-driver v1.2.3

Changes

• Declare direct MCP tool mounting. Relay tools are mounted through load_tool.
• Provide readable English and Chinese plugin names that follow the application language.
• Allow OpenAgent Settings to override the package mounting mode with Direct, Relay, or Follow plugin declaration.

Requires an OpenAgent Runtime supporting plugin MCP mounting modes. Existing package IDs, permissions, tool names, and plugin data remain unchanged.

Qualified source: 896aa2c232c16c7d595738ace01f183ce821ef81. Native qualification covered light/dark themes and English/Chinese.

OpenAgent Cua Driver v1.2.2

English

• Add English and Chinese plugin metadata and localized launcher diagnostics.
• Read the current OpenAgent locale from the versioned host bridge.

中文

• 补齐插件元数据和启动器提示的中英文翻译。
• 通过带版本的宿主桥接读取 OpenAgent 当前语言。

openagent-cua-driver 1.2.1

Use the generic portable daemon contract without a Runtime implementation binding. Preserve explicit real-computer-access authorization and verified provisioning of the pinned driver.

Requires an OpenAgent Runtime implementing the current generic plugin contract and Host Bridge; older Runtime-bound or package-flow implementations are not supported by this package.

Validation: package validator and repository tests passed. Native installation, daemon supervision, and MCP probe passed in an isolated OpenAgent instance. The attached ZIP places plugin.json at the archive root.

v1.1.0

The package now provides the driver it runs.

bin/cua-driver.mjs resolves a driver in one order: OPENAGENT_CUA_DRIVER_BIN,
then the verified cache under PLUGIN_DATA/driver/<sha256>/, then a download of
the release pinned in bin/lib/pins.json. Nothing in 1.0.0 could produce a
driver at all — the launcher resolved a bare cua-driver on PATH, which the
host supplied only in development builds.

Pinned release

cua-driver-rs-v0.30.1 from trycua/cua, one asset and SHA-256 per platform
(windows-x86_64, windows-arm64, darwin-universal, linux-x86_64,
linux-arm64). The digest is checked before anything is extracted, so a
re-cut upstream asset fails the launch and reports both digests instead of
executing new bytes. The windows-x86_64 and linux-x86_64 digests were
measured locally against upstream's checksums.txt; the other three are
transcribed from the same release manifest and are unverified on this machine,
which a mistake would surface as a first-launch failure, not as a wrong binary
being run.

Prepare before serving

node bin/cua-driver.mjs --openagent-prepare

A supervisor waits for this process to listen, with a deadline unrelated to
the network. Provisioning measured 14642 ms cold against OpenAgent's 15000 ms
daemon deadline, which the host treats as a hang and kills. After a prepare the
same start measured 408 ms. --openagent-prepare fetches and verifies without
starting anything, and is never forwarded to the driver.

Also

• Archive extraction is implemented in the package and refuses absolute paths,
  .., escapes, ZIP64, symlinks, tar links, PAX, and GNU long names; the
  archive is staged so a failure leaves no half-installed driver.
• Failures are named and actionable: unset PLUGIN_DATA, an unpinned platform,
  no network, a digest that is not the pinned one, an archive without the
  driver. Set OPENAGENT_CUA_DRIVER_BIN to run a driver you already have.
• The release tar is reproducible, so these digests stay meaningful.
• 35 tests; validated with openagent-plugin-kit.

🤖 Generated with Claude Code

v1.0.0

Full Changelog: https://github.com/BANG404/openagent-cua-driver/commits/v1.0.0