mac-approve requires Accessibility and has no fallback, hard-blocking unattended agents

mac-approve is presented in install.md and in the skill text as the answer to Chrome's "Allow remote debugging?" prompt. It has its own prerequisite that isn't mentioned anywhere, and when that prerequisite is missing there is no fallback — an unattended agent is stopped dead.

Environment: macOS (Darwin 25.1.0), browser-harness 0.1.9 and 0.1.10, Python 3.14.7, local Chrome over CDP.

Repro

With Chrome running but remote debugging not yet approved, and the launching terminal app not granted Accessibility, run any browser-harness script:

browser-harness: Chrome is asking "Allow remote debugging?" — run `browser-harness mac-approve` in another shell or click Allow to continue.
browser-harness: permission-blocked: wait for the user to click Allow in the Chrome permission popup before retrying.

Follow the instruction:

$ browser-harness mac-approve
accessibility-required: allow the app launching browser-harness (for example Terminal, iTerm, or Codex) in System Settings > Privacy & Security > Accessibility

--doctor at that point:

[ok  ] chrome running
[FAIL] daemon alive — see install.md
[FAIL] active browser connections — 0
[ok  ] Browser Use cloud auth — stored

Upgrading 0.1.9 → 0.1.10 changed nothing. The only thing that unblocked it was a human clicking Allow in the Chrome window.

Why it matters

The whole point of the harness in an agent context is unattended operation. Every other failure mode I hit in this session had some workaround; this one has none. The agent can detect that it is blocked but cannot act on it, and cannot even tell the user what single step will fix it, because the first blocked message doesn't mention Accessibility at all.

Suggestions

• Try an AppleScript / System Events path to click the button before requiring Accessibility.
• If neither route is available, say so in the first blocked message rather than after the user has already tried mac-approve and hit a second wall.
• Make the Accessibility message complete: it says to open System Settings, but not that you must then re-run mac-approve, nor that Chrome has to still be showing the prompt at that moment.
• Docs: install.md and the skill both describe mac-approve without noting its prerequisite.