macOS ScreenCaptureKit display_count=0 capture issue

NousResearch/hermes-agent · cluster 67162 · agent

Data as of

Nothing open on GitHub. Fix merged in #74175. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #74175. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Reports and fixes related to cua-driver on macOS returning zero displays or silent 0x0 captures via ScreenCaptureKit despite TCC permissions appearing correct. Involves both bug reports and proposed fixes for vision capture behavior.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #74175 fix(computer-use): normalize cua-driver result envelopes (salvage #63037, #57961, #73007)

    merged to main

    files: contributors/emails/[redacted:email], tests/tools/test_computer_use.py, tools/computer_use/cua_backend.py

  • #87333 fix(computer-use): placeholder-id targeting + macOS zero-display diagnosis (salvage #81340, #52949, #67259)

    merged to main

    files: tests/tools/test_computer_use_display_count_guard.py, tests/tools/test_computer_use_placeholder_ids.py, tools/computer_use/cua_backend.py, tools/computer_use/doctor.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #67259 fix: cua-driver macOS ScreenCaptureKit display_count=0 — surface actionable errors instead of silent 0x0 captures · superseded by another PR → 460d345, #87333, #74175
Closed issues · 2
  • Closed#67162cua-driver macOS: ScreenCaptureKit display_count=0 despite TCC permissions OK (macOS 26.5.2 arm64)
  • Closed#67165[Bug]:cua-driver macOS: ScreenCaptureKit display_count=0 despite TCC permissions OK (macOS 26.5.2 arm64)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Subsystem
agent
Merged PRs
#74175, #87333
Closed issues
2
Attempts
1 PR closed without merging
Fix link checked
16 Aug 2026

For your agent

The same facts, typed.