Remote Security

Public active gate

Screen viewing is live. Native input stays gated.

Short-lived sessions, one-time pairing, visible desktop consent, TURN-backed WebRTC, allowlisted commands, audit events, and emergency stop are implemented. macOS mouse and keyboard control still requires a signed native host, Accessibility permission, and stronger passkey enforcement.

Gate

Pairing code expiration

required

Gate

Visible desktop consent banner

required

Gate

Phone and desktop emergency stop

required

Gate

MFA or passkey before active control

required

Gate

Device registry with revoke

required

Gate

Session audit trail

required

Gate

Allowlisted CLI commands only

required

Gate

No public owner credentials

required

Gate

No unattended control by default

required

Gate

Security review before screen input ships

required