cua-driver

Use launch_app with the app's bundle id to start it in the background, then call get_window_state to snapshot its accessibility tree and act via element_index clicks. Never use the open CLI or AppleScript activate, which always foreground the target.

Resolve the default HTTPS browser bundle id from LaunchServices, then call launch_app with that bundle id and the urls array. This opens a new background window using the user's normal logged-in profile, avoiding the focus-stealing Cmd+L omnibox flow.

Keyboard commit events reach the app but renderer focus is not established on minimized windows, so Return fires as a silent no-op or system beep. Use set_value to write the field directly, or AX-click a Submit or Go button instead.

Element indices are cached per (pid, window_id) pair and replaced on every snapshot, so indices from a previous turn or a different window are stale. Call get_window_state with the same window_id in the same turn before acting.

No. OpenClicky's managed runtime does not expose recording or replay tools in this build. For regression evidence, save screenshots, logs, and a plain-language step list instead of attempting trajectory capture.

Canvas and custom-drawn surfaces are not reachable through the accessibility tree, so element_index actions fail. Coordinate clicks are only valid through explicit OpenClicky pixel routes; otherwise the agent should stop and report the missing capability.