Remote access

codeout opens a public tunnel by default so you can reach your sessions from anywhere. If you prefer to keep your traffic on your own network, codeout makes that easy without ever weakening the encryption or exposing your home address.

The model

There is no relay in the middle. The daemon listens locally; your paired devices connect to it. By default, codeout stands up a tunnel so you can connect from anywhere, but the channel stays encrypted end to end across it. There are three ways to provide that transport:

codeout (default)

Zero configuration. codeout.dev stands up a tunnel for you and gives you a stable public address to pair against.

codeout --local

Same LAN or same tailnet. Nothing exposed to the internet. The device reaches the daemon locally.

Self-hosted tunnel

Your own Cloudflare Tunnel, SSH reverse tunnel, or reverse proxy. You own every hop.

Direct, on the same network

When you want to keep everything off the public internet, run codeout --local. The daemon binds to loopback and your LAN, your device dials it directly, and nothing leaves the network. Run this way, you pair a device on the same Wi-Fi or VPN, and you are done.

Direct, over Tailscale

A private mesh VPN is the cleanest way to extend that direct connection beyond the LAN. Install Tailscale on the daemon host and on your devices, sign in to the same tailnet, and your phone reaches the daemon over its tailnet address as if it were on the LAN. Start codeout with --local for no exposed ports, no tunnel, and no third party in the path.

daemon host
# install and join your tailnet
$ tailscale up
# find this host's tailnet address
$ tailscale ip -4
100.x.y.z
# reach the daemon from any device on the tailnet
http://100.x.y.z:8400

One-command tunnel

By default, codeout runs with a public tunnel. codeout.dev runs the tunnel endpoint for you, hands you a stable public URL, and your daemon connects out to it.

~/projects/app
$ codeout
  opening tunnel (codeout.dev) ... ready
  Pair a device  scan the QR, or type the code
    address      https://amber-cedar-204.codeout.dev
  Reachable from anywhere via the tunnel above. The link stays end-to-end encrypted.

Pair against the public address and you are reachable from anywhere with a browser. This is the easiest remote option, and it is still private, for the two reasons below.

Your home IP is not exposed

The daemon dials out to the tunnel. It does not accept an inbound connection from the public internet, so there is no port to open on your router and nothing for the public to scan. The world only ever sees Cloudflare's address, never yours. Compared with opening a port and pointing a DNS record at your house, this is genuinely more private: your home address never appears on the wire that strangers can see.

The tunnel only opens for paired devices

Over the public tunnel the daemon accepts only a paired-device token plus the end-to-end-encrypted channel. The plaintext path is refused and the owner token is refused; both are local-only. So a leaked tunnel URL is just an address, and even a leaked device token cannot derive the session keys, which never leave the device. The worst the public side gets is a locked door and some ciphertext. The full gate is on the Security and encryption page.

Self-host your own tunnel

Prefer to own every hop? Any tunnel that forwards to the daemon's local port works. Run your own Cloudflare Tunnel, an SSH reverse tunnel, or a self-hosted reverse proxy, point it at localhost:8400, and pair against its address.

daemon host
# example: an SSH reverse tunnel to a box you control
$ ssh -R 8400:localhost:8400 you@your-vps
# then pair against your-vps:8400

The encryption holds regardless

Important

A tunnel only moves bytes. It never gets the keys. The device-to-daemon channel is encrypted end to end, so there is no relay required, and any tunnel only ever sees encrypted blobs. A public tunnel, a curious proxy, or codeout.dev itself sees nothing but sealed ciphertext. Pick the option you trust to keep your daemon reachable, not to keep it private. Privacy is already handled by the encryption.

That is the load-bearing point of this whole page. The transport is interchangeable precisely because it is untrusted by design. You are choosing how the traffic travels, not who gets to read it, because the answer to who gets to read it is always: only your daemon and your device.

Binding and ports

default port
8400
default bind
loopback and LAN, though the default tunnel dials out so you do not need inbound ports open. For a local-only setup without the tunnel, use codeout --local.
going remote
prefer a VPN or an outbound tunnel over binding to a public interface. The encryption holds either way, but a closed inbound port is one less thing to think about and one less thing to scan.