Codee Remote Viewer
Phone browser pairs with the user's own desktop host and receives the owner-approved WebRTC screen stream. Native touch, mouse, and keyboard control stay locked until the signed host gate is complete.
live consent-based viewer
Codee Remote
Two separate remote tracks
See the desktop when you need eyes. Send commands when you only need Codee.
Codee Remote is split on purpose. The Remote Viewer is the phone-to-desktop owner console with Codee tools inside it. The Remote CLI Bridge is the safer command lane for `doctor`, `scan`, `support`, `test lane`, and deploy proof.
Codee Remote CLI Bridge
Phone sends allowlisted Codee commands to a paired desktop workspace. Output returns to the portal with audit events and proof reports.
allowlisted commands
Control Plane
Cloud Run API, session storage, device registry, Pub/Sub command queue, Cloud Storage proof artifacts, Firebase Hosting, and Secret Manager.
WebRTC and TURN
The viewer uses Codee's authenticated signaling API and the running TURN relay for cross-network screen delivery.
Desktop Host and Bridge
The downloadable host creates short-lived cloud sessions and runs exact allowlisted Codee commands. The browser host asks the owner to choose a screen before sharing.
Public Active Gate
Remote desktop control stays locked until consent, revoke, audit, MFA/passkey, and emergency stop pass.
Local proof commands
python3 codee.py remote plan . --write --force python3 codee.py remote installer . --write --force python3 codee.py remote host . --write --force python3 codee.py remote viewer . --write --force python3 codee.py remote bridge . --write --force python3 codee.py remote pair . --device-name "My Desktop" --write python3 codee.py remote security . --write --force python3 codee.py remote demo . --write --force python3 codee.py remote readiness . --write python3 codee.py remote status .