What happened
Cua’s changelog for the week of November 2, dated November 2, 2026, groups updates across Cua Driver and Lume. The headline infrastructure item is “Compat gateways for E2B and Daytona, Hetzner as your own cloud, the elastic pool, cua share and the public relay.” The entry is associated with issue #5778. The changelog does not explain the gateway compatibility model, what configuration is required, or how the elastic pool allocates computers. It also does not give prices, quotas, regional availability or service-level commitments for these options.
The same changelog lists changes to Cua Driver versions 0.39.0, 0.40.1, 0.40.2, 0.40.5, 0.40.6, 0.41.0 through 0.41.3, 0.43.2 and 0.44.0, with full details linked to GitHub. Among the listed features, macOS actions can skip the post-action window-change wait; get_window_state can return JPEG screenshots encoded from raw pixels; and Linux Wayland gains a niri compositor adapter. Cursor behavior is also adjusted: a plain, upright agent cursor is the default, while visual effects and marks are opt-in. A “fast path with act-time target guards” is behind a default-off flag, and refusal of ungranted macOS Automation scripting is opt-in.
The changelog includes further platform-specific changes. Cua Driver can capture the KWin desktop through ScreenShot2 behind a kwin-capture option, and it adds a desktop entry for the installation that owns the CLI. The list also describes permission and safety work, including scoping launch_app to granted app resources and holding tool routes while runtime admission awaits permissions. These entries identify implementation work, but do not provide user-facing setup steps or explain which releases include each change.
For Lume, the changelog names version 0.7.0. Its features include lume cp for transferring files between host and guest, installing source builds as lume-local beside the released Lume, and experimental features behind experiments: “Ask first,” CI runners, TCP shares, secure networks and the phone app. Lume’s listed fixes include allowing a VM to stop without ending the server and reaching macOS VMs over vsock rather than local-network or VPN routes. The announcement directs readers to GitHub for full details, but the changelog itself does not document activation, compatibility requirements or a migration path.
What the archive adds
New Runtime’s earlier coverage on Cua’s Spaces SDK described per-agent desktops, while its October 30 note covered E2B, Daytona and Hetzner backends. This is a new update to a continuing product story: the November changelog adds a broader cluster of infrastructure options and detailed Driver and Lume changes, rather than simply announcing the initial Spaces SDK.
Trend signal
This update supports the pattern agent-ready software exposes capabilities: Cua is presenting computer environments and interaction functions as selectable infrastructure for agents. The evidence is suggestive rather than conclusive. The changelog names backends, sharing and relay options, but does not describe their permission boundaries, interfaces or how external agents compose them.
Why now
The November 2 changelog follows Cua’s October Spaces updates, which also named E2B, Daytona and Hetzner. The sequence makes this update relevant as a continuation of Cua’s computer-runtime development. The company does not explain why these additions are being released now or identify a specific customer demand behind them.
Why it matters
A computer-using agent depends on more than its model: it needs a desktop, a way to interact with that desktop, and a runtime that can be provisioned and controlled. More backend choices can give teams flexibility to match environments to their infrastructure, while sharing and relay options may open different ways to connect agents with computers. Those are possibilities suggested by the feature names, not demonstrated outcomes in the changelog.
The Driver changes also touch practical reliability and control. Screenshot encoding, compositor support and permission-scoped actions can affect what an agent observes and which actions it is allowed to take. But teams should not infer that a particular workflow is now reliable or secure simply from a feature entry. They need to test the exact operating system, grants, backend and interaction path they plan to use. The update is most useful as a shortlist of capabilities to investigate, not as evidence that one deployment configuration is production-ready.
Limits and uncertainty
Cua’s changelog is a feature and fix list, not a full product announcement. It does not state when the infrastructure options become generally available, how to enable them, or whether each is included in a particular plan. It supplies no comparative latency, reliability, security or cost measurements for E2B, Daytona, Hetzner, elastic pool, Cua Share or the public relay. The listed Driver and Lume changes also lack detailed compatibility and migration guidance on this page. The changelog points to GitHub for full details; teams should verify the relevant release notes and test their own setup before relying on a capability.
Skill to build now
Create a small backend acceptance test for one computer-use task your agent already performs. Run the same task in the environment you use today and, if you have access, one alternative backend named by Cua. Record provisioning success, screenshot readability, action completion and cleanup behavior. Treat this as your own comparison: Cua’s changelog gives no benchmark or promise that these backends behave identically.
Reader takeaway
Cua’s November update expands the computer-runtime options it names and adds Driver and Lume capabilities, but it does not establish which option is best or ready for a given workload. Use the changelog to identify a candidate environment, then validate permissions, interaction behavior and operational fit in your own agent workflow.