Remote access

Run /webui and scan the relay QR code with your phone browser. No VPN or public listening port is needed.

Connect

1. Keep AtomCode running and run /webui. It opens the local browser and prints a phone link and QR code.
2. Scan with your phone browser, or copy the relay link from the WebUI Remote access dialog. The devices may use different networks.
3. The phone and TUI share the same conversation. /webui stop, signing out in the terminal, or exiting AtomCode stops relay sharing.

Standalone: atomcode webui. Local only: /webui --local or atomcode webui --local. Explicit /webui lan or --host <address> uses the local network instead of automatically connecting a relay.

Connection failures

Local access remains available if relay setup fails. The terminal and Remote access dialog explain the failure. If WebUI is unsupported, upgrade the relay server and install the matching WebUI assets, then retry /webui. Use ATOMCODE_APP_RELAY for a self-hosted relay and ATOMCODE_ENABLE_RELAY=0 to disable relay access.

Relay address

The default HTTPS relay is https://relay-atomcode.atomgit.com; no extra configuration is needed. On your phone, open the pairing link generated by AtomCode or scan its QR code.

Security and lifetime

The link grants access: keep it private. HTTPS protects transport; the local WebUI still checks its access token. The relay can process traffic; this is not end-to-end encryption. Pairing credentials survive reload in tab-scoped sessionStorage and are cleared when the tab closes. Network disconnects reconnect automatically. Access stops while the computer is asleep, offline, or AtomCode has exited.

Local network alternative

/webui lan remains available on the same Wi-Fi. /webui --host <virtual IP> also works with an existing VPN. These local HTTP connections require a trusted network.