cua-driver v0.2.0 is out. The headline change is practical: the release tarball ships as a universal binary, meaning a single package covers both Apple Silicon (arm64) and Intel (x86_64) Macs. You do not need to pick an architecture-specific build.
The checksums are published alongside the release. The Darwin arm64 package (cua-driver-0.2.0-darwin-arm64.pkg.tar.gz) hashes to a6e8b598c5e9c311039d9c8784dd9b5bf208d95bb7c57d2e96b1dcac2769fd79. The plain tarball (cua-driver-0.2.0-darwin-arm64.tar.gz) hashes to 18c9fb20dcddfe703a55ed99aede4ca3d8fe5aee38afd20c3731acb10f6f4478. Verify before you deploy.
Installation is a single command:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/trycua/cua/main/libs/cua-driver/scripts/install.sh)"
The script pulls from the main trycua/cua repository and handles the setup for you. No manual architecture detection required.
The version bump itself was automated through GitHub Actions, which keeps the release cadence mechanical and auditable. That matters for teams who care about supply-chain hygiene: the commit (d3f3b93) is traceable and the hashes are right there in the release notes.
For product engineers building on top of cua, the universal binary removes a common friction point. Teams running mixed Mac hardware (M-series workstations alongside older Intel machines, or CI runners that differ from developer laptops) no longer need to branch their install logic by architecture. One script, one binary, both platforms.
What to do today: If you are already on an earlier version, run the install script above and verify the SHA against the published checksums. If you are evaluating cua-driver for the first time, the universal binary and single-command install lower the barrier to getting a local environment up quickly.