Cua Driver 0.19.0 puts browser control below the agent, killing the Chrome-extension dependency

Cua Blog·medium signalXBlueskyLinkedInCopy link

Released August 6, Cua Driver 0.19.0 binds an exact Chromium tab to its native process and window via the Chrome DevTools Protocol, giving agents page-aware browser actions and full desktop control in the same session — reachable through CLI, MCP, Python and TypeScript without the agent host owning a browser integration. That contrasts with Claude Code, which connects through a Chrome extension sharing browser state, and Codex, which ships an in-app browser separate from the user's regular Chrome profile. Attaching an existing signed-in profile requires an explicit launch grant rather than a runtime modal, so authorization is set at the policy layer; stable on macOS, Windows and validated Linux configurations.