You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
computer-use macOS: request_access reports screenshot/accessibility available when the host lacks the grants; failures do not name the missing permission #5917
request_access on the macOS backend claims capabilities the host process does not have. Driving the bundled server directly over stdio from a host that lacks Screen Recording and Accessibility grants (receipt 2026-09-06, crates/tui/plugins/computer-use at main 7fdb613b2):
request_access -> ok: true, capabilities: { screenshot: true, recording: true, accessibility_tree: true, clipboard: true, ... }
screenshot -> ok: false, error: "screencapture exited 1: could not create image from display"
get_app_state -> ok: false, error: "application not found — call list_apps for exact names/pids" (Calculator had just launched: launched: true)
key cmd+q -> ok: false, error: "osascript timed out"
The README promises the opposite: "request_access reports what is missing and every capability fails closed naming the missing tool or permission — it never guesses." Today it probes for the presence of screencapture/osascript, not for the grant, so an agent is told it can look and act, then fails on the first call with an error that does not name the missing permission (the key failure is a 25 s timeout, not "Accessibility not granted for ").
Fix
Screen Recording: probe with a real capture attempt (or CGPreflightScreenCaptureAccess via the JXA bridge) and report screenshot: false with missing: ["screen_recording"] and the host app name to grant it to.
Accessibility: probe AXIsProcessTrusted() through the bridge; when false report accessibility_tree, key, type, click as unavailable with missing: ["accessibility"], and make key/type fail immediately with that reason instead of timing out.
open_application returning launched: true followed by get_app_state "application not found" 1.5 s later: either wait for the process to appear before returning, or return the pid so the caller can target it.
What happens
request_accesson the macOS backend claims capabilities the host process does not have. Driving the bundled server directly over stdio from a host that lacks Screen Recording and Accessibility grants (receipt 2026-09-06,crates/tui/plugins/computer-useat main7fdb613b2):The README promises the opposite: "
request_accessreports what is missing and every capability fails closed naming the missing tool or permission — it never guesses." Today it probes for the presence ofscreencapture/osascript, not for the grant, so an agent is told it can look and act, then fails on the first call with an error that does not name the missing permission (thekeyfailure is a 25 s timeout, not "Accessibility not granted for ").Fix
CGPreflightScreenCaptureAccessvia the JXA bridge) and reportscreenshot: falsewithmissing: ["screen_recording"]and the host app name to grant it to.AXIsProcessTrusted()through the bridge; when false reportaccessibility_tree,key,type,clickas unavailable withmissing: ["accessibility"], and makekey/typefail immediately with that reason instead of timing out.open_applicationreturninglaunched: truefollowed byget_app_state"application not found" 1.5 s later: either wait for the process to appear before returning, or return the pid so the caller can target it.