[Feature] Let Cowork computer-use share a single cua-driver daemon instead of claiming the session exclusively

Environment: Windows 11, Claude Desktop (Cowork), NVIDIA GPU (display via HDMI on the dGPU).

Problem: Claude Desktop's bundled cua-driver starts its own instance over stdio and claims the desktop capture/input session exclusively. When a second cua-driver-based agent is present on the same machine (in my case Nous Hermes, which uses the same trycua cua-driver), one side gets black / 0x0 screenshots. A stray cua-driver-serve autostart scheduled task made it worse until I disabled it. After cleanup, single-agent use works — but the two agents cannot run simultaneously: whichever grabs the driver locks the other out.

Why this should be fixable: cua-driver is designed for concurrent multi-agent use — each connection gets its own session id and its own synthetic cursor when agents connect to one shared daemon over HTTP/socket. Cowork, however, bundles its own driver over stdio, holds the session exclusively, and exposes no user setting to attach to an external/shared daemon.

Request: add an option for Cowork's computer-use to (a) attach to an already-running cua-driver daemon instead of spawning an exclusive one, and/or (b) not hold the desktop session exclusively — so multiple computer-use agents can co-work on one machine, matching cua-driver's multi-cursor design.

Impact: today only "one agent at a time" works; this would enable running Cowork alongside another cua-driver agent concurrently.