1. Telemetry& privacy expectations
- “Fair criticism… we took a similar approach to established dev tools like Homebrew, with an anonymous, opt‑out telemetry… we should make the opt‑out path clearer.” — frabonacci
- “The problem with opt‑in telemetry is that 95 % of users don’t change defaults… only a subset of them will turn it on.” — jorvi
2. Technical merit & use‑cases of Cua Driver
- “Being able to run multiple UI automation tests simultaneously was the big win.” — LatencyKills
- “You could definitely build a test framework on top of it… you can launch an app without raising/focusing it.” — frabonacci
- “Background driver sounds like the missing middle ground” for agents who want “supervised direct access” instead of full VMs. — prashant3210
3. Broader implications for agent frameworks
- “If Apple doesn’t make this more first‑class, Linux/Android‑style environments may move faster.” — frabonacci
- “I did something similar on Windows by creating a virtual desktop… reimplement RemoteApp without a dedicated server.” — hexmiles - “What is specific about this for using with agents? … If you want to use it directly as an automation library, you can take a Swift dependency on ‘CuaDriverCore’.” — pimlottc