Qwen splits its computer-use driver into its own package

Qwen pulled the computer-use driver out of qwen-code and released it as its own binary and npm package. Version 0.20.0 of cua-driver-rs, published August 24, ships a codesigned and notarized macOS universal binary plus a QwenCuaDriver.app, per the release notes. It also ships unsigned Linux builds for x86_64 and arm64, requiring at least glibc 2.31, along with Windows builds. A single @qwen-code/cua-sdk npm package wraps all of it.

That matters for anyone building agents that click around a screen instead of just calling APIs. Computer-use drivers are the layer that translates model output into mouse and keyboard actions. This one used to live inside qwen-code as an internal dependency, and pulling it into its own package with its own release cadence and signed binaries is what you do when you expect other projects to import it directly.

Two new environment flags came with the split. CUA_DRIVER_RS_COORDINATE_SPACE=1 switches the driver to relative coordinates instead of absolute screen pixels, useful for running an agent across displays with different resolutions or scaling. MCP_MODEL_PAYLOAD_FILTER=1 filters MCP payloads down to text, which reads as a fix for tool calls that were passing along more than models needed.

Only the macOS binary and app bundle got the signing and notarization treatment. The Linux builds ship unsigned, a real constraint for anyone deploying in an environment with code-signing requirements. The release notes don't say whether Windows builds are signed, or whether signed Linux builds are coming, so treat both as open questions.