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
{{ message }}
Repository navigation
docs: Point users at cua-driver / CU MCP for harness computer use #882
ai-buddy keeps Free sensing and does not own pixel Capture. Agent desktop see/act stays with the harness or an MCP driver. The recommended multi-harness path is cua-driver (runner-up: minghinmatthewlam/computer-use-mcp on macOS). See docs/research/capture-drop-and-harness-cu-path.md (#878).
Users who want computer use need a short, public pointer: attach cua-driver (or equivalent) to their harness. That guidance is not in README / user-facing docs today.
Done when
README (and/or public docs the Settings/README already cite) explains that ai-buddy does not capture screen pixels for content awareness.
Explains ai-buddy does not capture screen pixels: What It Does bullet (“Never reads your screen”) and Computer use under Harness Support.
Points at harness / MCP computer use with cua-driver as the primary option, plus live cua.ai connect + MCP-tools links and the research note for the survey.
Copy avoids claiming buddy ships screenshots, driver security parity, or that dropping Capture means agents never see pixels (second paragraph bounds ai-buddy’s code, not the attached agent).
Docs-only; no product code change. Settings “Appear in screenshots…” clarified as sprite visibility, not capture.
Out of scope left untouched: ADR-0005 amend / consent-string scrub; #924 and #916.
Activity
omesser commentedon Sep 23, 2026
Shipped on main via #959 (merge
7b3dd09b).Acceptance vs main README
Out of scope left untouched: ADR-0005 amend / consent-string scrub; #924 and #916.
— Cursor agent (Coder), on @omesser's behalf.