Mobile Handoff
Codux Mobile pairs with the desktop host so you can step away from the desk and keep going on your phone. The desktop app remains the real terminal host. The v3 remote stack uses short-lived relay tickets for pairing, prefers WebRTC DataChannel when direct transport is available, and falls back to WebSocket relay when P2P cannot connect.
Components
Section titled “Components”| Component | Purpose | Download |
|---|---|---|
| Codux Desktop | Main app for projects, terminals, Git, stats, memory, and remote hosting. | Desktop Releases |
| Codux Mobile | Android and iOS companion: pair with the desktop, share split terminals, browse and edit text files, upload images. | Mobile Releases |
| Codux Relay | Ticket exchange, WebRTC signaling, and WebSocket fallback. Leave Relay empty for the global node, or set a regional/custom relay when needed. | Relay Guide |
Relay configuration
Section titled “Relay configuration”Configure Settings → Remote like this:
| Mode | Value |
|---|---|
| Global public node | Leave Relay empty, or use https://codux-node.dux.plus |
| China node | https://codux-service.dux.plus |
| Custom v3 relay | Your own relay URL |
After changing the relay value, pair the mobile client again so the QR code and host info reflect the new network path.
What Mobile Can Drive
Section titled “What Mobile Can Drive”The desktop host exposes these remote operations:
- Project list, project add/edit/remove.
- Shared desktop terminal list, terminal create, input, resize, interrupt/escape, close, and buffer replay.
- Terminal uploads: images are written to a temporary upload folder and inserted into supported AI tools through clipboard paste or file path insertion.
- File list, UTF-8 text file read/write, same-directory rename, and delete.
- AI stats payloads for the selected project, including live sessions, heatmap, time buckets, tool breakdown, and model breakdown.
Transport: WebRTC first
Section titled “Transport: WebRTC first”Codux Mobile starts from a short-lived ticket generated by the desktop app. After pairing, the client receives transport candidates and uses WebRTC DataChannel when it is healthy. If direct transport is unavailable, the same protocol continues over WebSocket relay.
Encryption model
Section titled “Encryption model”Terminal input, output, file payloads, project lists, and AI stats are protected by Codux’s paired-device encryption envelope. The relay helps with pairing, signaling, and fallback transport; it does not become the desktop host or decrypt terminal content.
For teams that need a private or regional path, use a custom Codux relay. For most users, leaving Relay empty uses the global public node.