Custom Codux Relay
Codux Mobile connects through the v3 remote stack. The desktop app is still the terminal host; the relay handles short-lived pairing tickets, WebRTC signaling, and WebSocket fallback when direct transport is unavailable.
Recommended settings
Section titled “Recommended settings”Open Codux → Settings → Remote on the desktop app:
| Need | Relay value |
|---|---|
| Global public node | Leave empty, or use https://codux-node.dux.plus |
| China node | https://codux-service.dux.plus |
| Team/private relay | Your own v3 relay URL |
After changing the relay value, pair the mobile client again. The QR ticket and host info need to reflect the current network path.
When to use a custom relay
Section titled “When to use a custom relay”- Your phone and desktop are often on networks where the public path is slow or blocked.
- Your team wants pairing/signaling metadata to stay on controlled infrastructure.
- You want a relay close to your users for lower latency.
What the relay does not do
Section titled “What the relay does not do”- It does not run your terminal.
- It does not store AI sessions, memory, or project files.
- It does not replace paired-device encryption.
More AI CLI tools, database profiles, and additional secure connectors are still being added through Codux’s driver architecture. They are not required for mobile pairing.