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 screen/control product. The Remote CLI Bridge is the safer command lane for `doctor`, `scan`, `support`, `test lane`, and deploy proof.

Open Viewer Plan Open CLI Bridge Installer Demo Security Gate Remote Manifest

Track 1

Codee Remote Viewer

Phone browser pairs with the user's own desktop host, then shows a consent-based screen stream. Touch and mouse input unlock only after approval.

phone-to-desktop viewer

View Track

Track 2

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

View Track

Backend

Control Plane

Cloud Run API, session storage, device registry, Pub/Sub command queue, Cloud Storage proof artifacts, Firebase Hosting, and Secret Manager.

Streaming

WebRTC and TURN

The viewer needs WebRTC signaling and a TURN relay. The CLI bridge can launch first with a command queue and no video relay.

Installer

Desktop Host Skeleton

Downloadable host foundation writes state, queue, audit, and safety files without screen streaming or owner credentials.

Install Track

Security

Public Active Gate

Remote desktop control stays locked until consent, revoke, audit, MFA/passkey, and emergency stop pass.

View Gate

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 .