Repository navigation
docs(rfc): propose remote Computer Use for a connected Mac - #21981
Conversation
7319393 to
d9c1f0b
Compare
UX Review (Opus 5.5, fork) — ⏭️ skippedRevision |
First Principles Review (Opus 5.5, fork) — ⏭️ skippedRevision |
Design Review (Opus 5.5, fork) — ✅ PASSDesign-level review of Design-Verdict: PASS This adds only a draft RFC and its index row. It keeps Computer Use ungoverned, and the code seams it cites are on the base tree. [DESIGN-REVIEWED] 5cf9211 Description read[DESCRIPTION-READ] 2124eead96af0f29df680db57f47611ecac9f43077c2ce6c0bf30fccdaa759be 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 |
GPT 6.1 Review (fork) — ✅ no blocking findingsReviewed Review detailsNo findings. |
Opus 5.5 Review (fork) — ✅ no blocking findingsReviewed |
050285d to
2366de2
Compare
2366de2 to
dc4daef
Compare
dc4daef to
9ae984c
Compare
9ae984c to
706d412
Compare
2b02c48 to
a33f516
Compare
c4092aa to
58209c3
Compare
58209c3 to
fcc3cb2
Compare
fcc3cb2 to
f0c624c
Compare
…Tunnel mode A Linux gateway cannot drive desktop apps today, and in the recommended setup the apps live on the Mac the desktop app runs on. The RFC splits Computer Use at the backend seam: the chokepoint stays on the gateway, a Mac-side executor supervised by the desktop app runs the macOS driver and re-checks every floor that has no config key, and the app pulls requests over its existing tunnel with an SSH-minted, route-scoped credential.
iamwhatever
left a comment
There was a problem hiding this comment.
APPROVE -- reviewed 5cf9211.
This is docs only: a draft RFC plus its index row, with no code, config or route change. Approving it records the proposal; accepting the design remains a maintainer decision, as the Goal says. The security section is candid about the residual risks: the Mac switch is the only key against a compromised gateway, the typed-text scan is a pattern check, and the ssh localhost gap is the existing one. The symbols I spot-checked on current main exist where described.
One nit, non-blocking: _STRICT_INTERNAL_API_PATHS now lives in dashboard/server_internal_paths.py, not server.py.
All AI lanes are clean and checks are green; I read the document and CI and ran nothing.
— crew-pr-reviewer (r119)
|
@iamwhatever Confirmed. |
|
Use case from a headless Linux gateway on EC2. It has no inbound SSH port, so my Mac would reach it through an ssh-config Host entry whose ProxyCommand runs
|
Problem / Motivation
Goal: Record a design, for maintainers to accept or reject, that lets a gateway on a headless Linux host drive native apps on the Mac whose desktop app is connected to it.
The setup the docs recommend runs the gateway on a remote Linux host and the person on a Mac in Remote Tunnel mode. In that setup Computer Use cannot be turned on: Settings shows
LINUX_REASONand no toggle, the spec gate never advertises the tools, and the apps the person wants driven are on the other machine anyway. Running a second gateway on the Mac works, but splits memory, crons and sessions across two crews.Why it matters
Computer Use is unavailable to everyone on the recommended remote setup. The design touches the Computer Use security boundary (a remote party gains input synthesis on a laptop), so it needs a recorded decision before any code lands.
Not a goal
What changed (motivation → approach → change)
Adds
docs/request-for-change/rfc-remote-computer-use.md(statusdraft, measured at310ad48b5f) and its row indocs/request-for-change/README.md.RemoteExecutorBackendon the gateway forwards each backend method; keystone, policy, index, fingerprint, refusals and audit stay on the gatewayThe approach reuses the browser panel's outbound-pull pattern and the existing backend swap seam rather than moving dispatch to the Mac, which would fork the audit, the operator policy and the second caller of
dispatch_tool. Four phases follow, each with pass/fail exit criteria, starting with a probe of whether a desktop-app child inherits the app's macOS permission grants.Backwards compatibility
Compatible: documentation only; no code, config or route changes.
Removes nothing: the diff adds one document and one index row.
Tests
N/A: documentation only.
scripts/docs_lint.pypasses.Manual verification
Every claim about current code was checked against
310ad48b5fwithgit showandgit grep. None of the cited files changed between that commit and this PR's base.Related Issues
no linked issue: the RFC is the first artifact; implementation PRs will reference it.
Checklist