Platform support

Proven operating systems, Linux window systems, and browser routes, with known boundaries and remaining work.

A capability counts as supported only when a Rust harness test observes the result in application- or desktop-owned state (see How Cua Driver works). Unsupported routes return a structured refusal.

Operating systems#

Linux window systems#

"Wayland" is not one API: each compositor exposes different discovery, capture, activation, and input. Native Wayland is opt-in with CUA_DRIVER_RS_ENABLE_WAYLAND=1; without it, Wayland sessions use XWayland routes where the app has a real X11 window.

X11 window capture supports packed 16-, 24-, and 32-bit TrueColor and DirectColor images. DirectColor capture reads the window's current colormap for each frame, including palette changes that do not repaint the window. Other indexed visual classes remain outside the native capture path.

Distribution names (Ubuntu, Arch) do not matter much; what matters is the display session and the app's backend. A portal grant belongs to the runtime that received it and may prompt again after a restart.

Hyprland and Omarchy#

Omarchy is an Arch setup built on Hyprland. Modern Hyprland is not wlroots, so Sway results do not carry over. An optional Hyprland plugin, off by default and outside the normal installer, adds two independent agent seats (Cua-Agent, Cua-Agent-2) for isolated background input. Cua Driver 0.24.0 shipped it with a narrow qualification:

• Apps: Calc from libreoffice-fresh 26.2.5-3 and Inkscape 1.4.4-6, checked against package metadata before every action.
• The plugin's Hyprland ABI and compiler toolchain must match the compositor.
• Not covered: Chromium, Electron, and XWayland raw input; Unicode and IME; multiple layouts; modified pointer gestures.
• Explicit foreground actions change focus and pointer and do not restore them.

Evidence for this feature is recorded in PRs #3547, #3557, and #3572. General Hyprland support still needs an accepted input and permission design, packaged install and upgrade proof, and the full native catalog on an integrated candidate.

Browser routes#

Browser mutation always starts from an exact native (pid, window_id) binding.

Logged-in profile attachment is covered in Browsers.

Boundaries and remaining work#

These are operating-system boundaries, not bugs; the driver refuses instead of working around them:

• Windows integrity levels: a lower-integrity process cannot inject input into a higher-integrity (elevated) app.
• Standard Wayland: an ordinary client cannot send raw input to an unfocused, occluded window. AT-SPI actions still work in the background.
• macOS: off-Space SwiftUI trees, keyboard commits to minimized windows, and apps that accept only HID-tap input. Workarounds are in Troubleshoot.

Off-Space windows on macOS#

macOS omits windows on other Spaces from an app's AXWindows list. For AppKit windows, the driver recovers the requested window by its exact CGWindowID, so get_window_state, element actions, and background pixel actions keep working while the window stays on its Space. The user's current Space, frontmost app, and keyboard focus do not change. Recovery probes the first 2,000 accessibility element ids of the app; a window beyond that limit reports ax_window_unresolved. The agent cursor does not paint while an action targets a window on another Space. Windows virtual desktops and Linux workspaces do not yet suppress the cursor for off-workspace targets.

Desktop captures leave out the agent cursor#

get_desktop_state keeps the driver's own agent cursor and session pill out of the PNG it returns. Every response reports the outcome in structuredContent.agent_overlay_capture: excluded with the native method, not_present when no overlay pixels were on screen, or not_excluded with a reason.

Open evidence gaps, with no dates promised: broader WPF and WinUI 3 gestures, WebView2 native input, a controlled background_uipi_blocked fixture, more AppKit actions and SwiftUI popovers, real-Xorg multi-pointer, GNOME and KDE renderer catalogs, and the full nested-compositor catalog. A row changes only when an unchanged catalog cell produces new app-owned evidence at an exact source commit.