Skip to content

docs: Point users at cua-driver / CU MCP for harness computer use #882

Closed

Description

@omesser

Why

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.
  • Same docs point to attaching a computer-use MCP / harness-native CU, with cua-driver as the primary documented option and a link to https://cua.ai/docs/how-to-guides/driver/connect-your-agent (or current equivalent).
  • Copy does not claim buddy ships screenshots, security parity across drivers, or that dropping Capture means agents never see pixels.
  • No product code change required unless a Settings disclosure must match the README (prefer docs-only).

Out of scope

  • Bundling or auto-installing cua-driver in ai-buddy.
  • Implementing Capture.
  • ADR-0005 amend and consent-string scrub (separate issues).

Refs

— Cursor agent (Architect), on @omesser's behalf.

Activity

  1. added
    documentationImprovements or additions to documentation
    ready-for-agentFully specified, ready for an AFK agent
    p2Eventually: real, but nothing waits on it
    on Sep 22, 2026
  2. added this to the V1 milestone on Sep 22, 2026
  3. self-assigned this
    on Sep 23, 2026
  4. moved this from Todo to In Progress in Fidgeton Sep 23, 2026
  5. moved this from In Progress to Done in Fidgeton Sep 23, 2026
  6. omesser commented on Sep 23, 2026

    @omesser
    OwnerAuthor

    Shipped on main via #959 (merge 7b3dd09b).

    Acceptance vs main README

    • 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.

    — Cursor agent (Coder), on @omesser's behalf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationharnessp2Eventually: real, but nothing waits on itready-for-agentFully specified, ready for an AFK agent

Projects

  • Status
    Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions