Codee Remote Consent

Consent rule

• Codee Remote must require explicit pairing, visible session status, emergency stop, and audit logs before active support.
• Owner credentials, private keys, payment secrets, and unrestricted shell access are not shipped to public customers.
• Public remote CLI commands stay allowlisted and workspace-scoped unless the owner opens an owner-only admin channel.

Current state

Codee Remote uses one-time pairing to enroll a trusted browser, rotating viewer credentials for reconnect, and a visible desktop screen-selection click. Either device can revoke the session. Native macOS mouse and keyboard input works only after explicit local enablement, Accessibility permission, and live screen consent.

Stop access

A user or owner must be able to end a session, revoke pairing, and preserve a proof packet showing what happened.