macOS CUA Driver path and notarisation acceptance fix
Cluster 96328. Data as of
Nothing open on GitHub. Fix merged in #96341 on 27 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #96341. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #96341. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where the macOS computer_use feature rejects the current notarised CUA Driver and fails to locate it when installed via standard paths or symlinks. The fixes update the driver lookup and acceptance logic to handle notarised builds and common install locations.
Open issues0
Open PRs0
Fixes on record
-
#96341 fix(computer-use): launch notarised CUA Driver from standard macOS installs
files:
hermes_cli/config_defaults.py,tests/tools/test_computer_use_cua_macos_identity.py,tools/computer_use/cua_backend.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#96349 fix(computer_use): accept current notarised CuaDriver.app and ~/.local/bin shim (#96328) · superseded by another PR →
#96341,#96349
Closed issues · 1
- Closed#96328[Bug]: macOS computer_use rejects current notarised CUA Driver and misses symlinked app path
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #96341
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 27 Aug 2026