Repository navigation
docs: Say ai-buddy never reads pixels and point computer use at cua-driver - #959
Merged
Merged
Conversation
…river Closes #882. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
omesser
commented
Sep 23, 2026
ADRs are internal. A README reader has no use for the number and no reason to follow it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
ADR-0031 and
CONTEXT.mdalready record that ai-buddy drops Capture and keeps Free sensing, but the README never says it. A reader landing on the README gets one of two wrong answers. Either they assume the buddy screenshots them, which is alarming and false, or they assume desktop computer use is off the table, which is also false — it belongs to the Harness or to an MCP server they attach. Nothing public pointed at that path.What changed
Two README edits, docs-only. No product code moves; the Settings surface has no capture disclosure to contradict, only the existing "Appear in screenshots and screen shares" toggle, which is about the sprite being visible in captures rather than taking them, and the new copy says so.
describe_screendescribes layout), states the bound applies to ai-buddy's code and not to the agent attached to it, and names cua-driver as the portable option with both cua docs links.Judgment call: the runner-up stays out of the README.
minghinmatthewlam/computer-use-mcpis macOS-only and pre-1.0. A second name in user-facing copy forces a choice the reader has no basis to make, and the honest way to help them make it would be a security and maturity comparison the acceptance criteria rightly forbid. One primary option plus a link to the research note, which carries the full driver survey and the per-Harness table, unblocks the person who just wants this working and still leaves the survey one click away.Copy checked against the three things it must not claim. It does not say the buddy ships screenshots, it makes no parity claim across drivers (only one driver is named, and the caution attached to it is about its permission model rather than a comparison), and the second paragraph exists specifically to prevent "no Capture" reading as "agents never see pixels".
How to verify
Both external links fetched today, live, not just a 200 from an SPA shell:
https://cua.ai/docs/how-to-guides/driver/connect-your-agent— 200, no redirect,<title>Connect your agent to Cua Driver | Cua docs</title>. Body carries per-client registration sections for Claude Code, Codex, Cursor, Prime Agent and a generic MCP JSON block, and documents the Windows and Linux runtime, which is where the multi-OS claim in the copy comes from. The issue's URL is current; no path move.https://cua.ai/docs/reference/cua-driver/mcp-tools— 200, no redirect,<title>MCP Tools (macOS) | Cua docs</title>. Live. Worth knowing that this reference page is scoped to macOS even though the driver is not, which is why the copy introduces it as "lists what it exposes" rather than as the platform statement.pre-commit run --files README.mdpasses, codespell and ast-grep included.A reviewer can check the in-repo links resolve:
docs/research/capture-drop-and-harness-cu-path.mdand the#computer-useanchor generated by the new### Computer useheading.Notes
ADR-0031 is cited, not ADR-0005. The ADR-0005 amend and the consent-string scrub are separate issues and untouched here, as are the files #924 and #916 are editing.
Closes #882
— Claude Code agent, on @omesser's behalf.
🤖 Generated with Claude Code