Repository navigation
docs(rfc): carry remote computer use on the connected-computer socket - #40207
unstablebrainiac wants to merge 1 commit into
Conversation
UX Review (Opus 5.5) — ⏭️ skippedRevision |
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks: the change is a draft RFC revision in documentation only, it is reversible, and it adds no new governance row or pointer permit. Notes
[DESIGN-REVIEWED] 2eff5db Description read[DESCRIPTION-READ] f1f8d814569ca406672e645a9cecc5204f354a551b6f527946bf1b4a6f7d2135 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Review detailsNo findings. Notes:
[OPUS-REVIEWED] 2eff5db Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Code change approver recommendation: A person should decideWhy: the decider estimates a 10% chance that this change introduces a defect, within the 12% limit for approving on its own, but it changes 994 lines, more than the 400 it may approve on its own. Docs-only revision 2 of a draft RFC; status stays draft. I checked its code claims about connected computers against the repo and they match: protocol v1 with required root and confinement in Tier: 2, held for a person: design-doc-gate: D. An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit |
|
This adds a new concept, so it needs a design sign-off from a maintainer before it can merge. A maintainer will post the decision here. Review result on this head: no blocking findings. The diff touches only two Markdown files, and the RFC stays For the security review (the decision on these stays with the security reviewer and the maintainers):
Optional:
|
8a1b513 to
2eff5db
Compare
Problem / Motivation
Goal: Revise the remote Computer Use RFC so a Linux gateway drives a connected Mac over the connected-computer socket main already has, without a transport of its own and without hiding a local Linux driver.
RFC #21981 (
docs/request-for-change/rfc-remote-computer-use.md, statusdraft) was written before connected computers existed. It gave the Mac its own scoped bearer credential, six pull routes through the tunnel and an Electron channel. Since then the gateway half of connected computers landed (#34858): one authenticated socket per computer, dialled out over the same SSH forward, with a credential minted over the same SSH login. Built as written, the RFC would add a second tunnelled credential scheme for the same Mac. It also says nothing about a Linux gateway that has a local driver, which #35378 and #25222 propose.Why it matters
The RFC is the design every implementation PR for remote Computer Use cites. A design that duplicates connected computers' transport, or that would swap out a working local Linux driver, would be argued over in each implementation PR instead of once here.
Not a goal
draft; a maintainer records acceptance.What changed (motivation → approach → change)
Revision 2 of the RFC keeps the parts that do not depend on the transport and moves the transport onto connected computers.
computer-usechannel on the Mac's connected-computer socket; no new route or credentialThe RFC names what it needs from connected computers (a channel kind, a folder-less grant, a host-scoped channel, one confinement exemption for the fixed executor program) and asks those as open questions for the feature's author. Revision 1's own transport stays, condensed, as the fallback if a maintainer rules that Computer Use must not depend on connected computers. The phases are reordered so the backend seam, the codec, the Mac executor and the forwarding backend can land before any of connected computers' open PRs. The RFC index row and its audit note in
docs/request-for-change/README.mddescribe revision 2.Backwards compatibility
Compatible: documentation only; no code, config or route changes.
Removes nothing: the RFC's revision 1 transport is kept as its fallback section, and no code exists for it.
Tests
N/A -- docs only.
python3 scripts/docs_lint.pyexits 0, and the comment-history and brand checks pass.Proof: not provable -- docs or config only
Manual verification
N/A -- docs only. Every code claim in the RFC was re-read on main
1c37e326a2.Real-machine verification
N/A -- the diff changes two Markdown files and runs nothing.
Related Issues
Part of #40197
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...); PR Hygiene does not count commits