Scale computer-use 2.0 with open-source drivers, cross-OS sandboxes, and benchmarks for training, evaluation, and data generation.
Rust agentai-agentapplecomputer-usecomputer-use-agentcontainerizationcuadesktop-automationhacktoberfestlumemacosmanusoperatorswiftvirtualizationvirtualization-frameworkwindowswindows-sandbox
cua-driver permissions exists on macOS only; Windows and Linux have no TCC equivalent.
permissions statusis read-only and never prompts. It does not run the ScreenCaptureKit probe (macOS Tahoe can show a separate dialog for it), so it reportsscreen_recording_capturable: nullanddirect_capture_status: "not_checked", plus the last successfulpermissions grantverification when one is recorded for the running driver identity.permissions grantlaunches the installedCuaDriver.appthrough LaunchServices so the prompts attribute to the app, then requires a successful live capture probe. It never sends a prompt-capable request over the daemon socket.- Embedded hosts, in-process
CuaDriver.create()runtimes andcua-driver mcp --directown their own prompts: there,check_permissionsstays read-only even with{"prompt": true}. - After a grant changes, quit and relaunch the responsible app (
CuaDriver.app, or the host of a direct runtime).
See Permissions for the grant flow and recovery.