Cua Driver

You get a standardized loop: resolve the app by bundle ID, launch it, snapshot the window state, act through MCP tools like click or type_text, then verify the result. When accessibility trees are sparse (common in Electron and media apps), it falls back to screenshots and coordinate-based clicks or tries enabling debugging ports for DOM access. The permission model is explicit: you'll need to grant Accessibility and Screen Recording to the helper bundle. Honest take: this bridges the gap between Claude's reasoning and real GUI automation without writing AppleScript or wrestling with brittle selectors, though sparse trees mean you're sometimes clicking pixels and hoping.