Repository navigation
Require clear Remote Desktop pairing approval in setup #3
Description
Setup path
iOS Remote Desktop pairing plus Mac Remote Desktop pairing window.
Friction
The iOS pairing screen shows a Pairing code field, but that field is not used by the pairing request. The current happy path starts pairing, signs the challenge, and completes pairing from iOS; the Mac-side pending pairing approval UI is not part of that flow. This is confusing for setup and needs an explicit trust decision before public beta.
Expected
Make the pairing model clear and enforce it in the UI:
- If explicit Mac approval is required, keep the iOS user waiting for Mac approval and make the Approve/Reject buttons part of the flow.
- If bearer-token possession is intentionally enough, remove unused pairing-code UI and make the trust model explicit in setup copy.
Audit note
An escalation note was written to ops/agents/escalations/setup-audit.md because this touches Remote Desktop trust.
Activity
codepilotios commentedon Jul 1, 2026
Triage update (2026-07-01): marked
severity: highbecause this affects the Remote Desktop trust model before public beta. No code change made in this pass; maintainer decision is needed on explicit Mac approval vs bearer-token trust. Added toops/agents/escalations/issue-triage.md.codepilotios commentedon Jul 3, 2026
Maintainer decision (2026-07-03): Remote Desktop pairing must require explicit approval on the Mac. The iOS client must remain pending until the Mac user approves or rejects the device; unused pairing-code UI should not imply a trust mechanism that is not enforced. Implementation is approved.
codepilotios commentedon Jul 17, 2026
Resolved on main by merged PR #14. Pairing proof now enters a pending Mac-approval state, trust is persisted only after local approval, and the unused pairing-code field was removed.