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

The Codee Remote Viewer and toolbox are public-safe planning and owner-control surfaces. Full live screen streaming and input control remain gated behind signaling, TURN, device registry, MFA or passkey, signed host, consent, and audit proof.

Stop access

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