Repository navigation
agent: enable built-in computer use on Windows - #1383
Merged
Merged
Conversation
The pinned cua-driver-sdk already carries a Windows backend (UI Automation, SendInput, Windows.Graphics.Capture). Turn on embedded_cua for Windows and depend on the SDK there. Windows grants accessibility, input and capture to any process at the user's integrity level, so the requirement list stays empty and enabling computer use in Settings is the only consent step; the docs now say so, plus the Windows limits. Refs #1295 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Turns on built-in computer use (embedded cua-driver) for Maple Work on Windows. This is best effort: it has not been tested by hand on Windows yet. Refs #1295.
What changes
build.rsnow setsembedded_cuaon Windows as well as macOS and Linux.Cargo.tomladds Windows to thecua-driver-sdkdependency. It shares the macOS section, so a future SDK bump still touches two places, not three.2a397557, 0.38.0) already has a Windows backend: UI Automation, SendInput and Windows.Graphics.Capture. Upstream builds and ships it for x64 and arm64.Cargo.lockis unchanged.platform-windowswas already resolved in it.Consent on Windows
Windows has nothing like the macOS permission prompts. Any app running as the user can read UI Automation, send input and capture windows. So the requirement list is empty, and Settings shows the card as Ready with Enable. Computer use stays off until the user switches it on there, and each task still has its own switch. Those two switches are the only consent step. The docs now say this in so many words.
Known Windows limits (now in
docs/embedded-cua.md)ffmpegonPATH, the same as on Linux.Verification
cargo metadata --lockedpasses, so the lockfile needs no change.scripts/audit-sqlcipher-dependencies.py(cargo-deny advisories and bans) passes foraarch64-apple-darwin,x86_64-unknown-linux-gnuandx86_64-pc-windows-msvc.ci:windowslabel added:agent-windows: clippy-D warningson Windows, compilingplatform-windowsand the cua code. Passes.agent-full-windows: the native Windows test suite, 2,365 passed and 0 failed. The test binary links the SDK, and theagent::cua::drivertests that only build underembedded_cuaran on Windows. 43 minutes.agent-windows-updater: passes.ci:package), and anything that drives a real Windows desktop.Manual test after rollout
🤖 Generated with Claude Code