Access from outside
Clauder runs no cloud of its own and asks for no sign-up: the client talks straight to your server. So the whole question is how to reach it.

| How | What it takes | Good for |
|---|---|---|
| Local network | clauder --host 0.0.0.0 (or docker), an address like 192.168.… | home, the office, a TV in the kitchen |
| A tunnel outwards | the "Start tunnel" button in the app settings: cloudflared downloads itself, no account needed | "from anywhere" and with https right away — but the address is random and changes on restart |
| A VPN home | WireGuard or Tailscale on the phone, the machine's address inside the VPN | "from anywhere" with no open ports — the simplest honest option |
| Your own domain behind a proxy | a reverse proxy with https and your own auth | needed if you want Web Push in the browser: there is none without https |
| Telegram | just a bot token | no inbound route at all: the bot reaches out by itself |
Local network
By default the server listens on the loopback only — from outside it is invisible. Opening it to the phone is a deliberate act:
clauder --host 0.0.0.0In the app the same is done by a switch in the settings, on the "Application" tab. The same place lists the machine's addresses you can knock on — those are what travels to the phone by QR code.
A tunnel with one button
The app settings have "Start tunnel": cloudflared downloads itself, no Cloudflare account required. In return you get https immediately — and with it Web Push in the browser and the microphone, which no browser hands out without a secure context.
The price of that simplicity: the address is random and changes on restart. There is no permanent link here the way vendor-relay remotes have it — we deliberately don't run that infrastructure, it is a second product and a permanent on-call.
VPN
The most honest option for "from anywhere": WireGuard or Tailscale on the phone, and the machine is reachable at its internal address exactly as it is at home. No ports are exposed outwards at all.
Your own domain behind a proxy
If you already have a server with nginx and a certificate, Clauder goes behind a reverse proxy. All it needs is https — for Web Push — and your own auth on top, because Clauder's access key is not meant for a public address.
There is no TLS inside
The api itself speaks plain HTTP. Don't expose its port without a reverse proxy with auth — see Security.
What can actually be done from holiday
Not "looked at" — done:
- start a project in a new directory (the folder can be created on the spot) and begin a chat in it;
- hold a live conversation: messages, images, answers to the model's questions, model and effort changed on the fly, slash commands, interrupting and ending the session;
- pick up a session you started in the terminal in the morning and answer its question;
- look at project files, the output of a running command, a subagent's feed;
- see what is left of the plan limits and not start a big task for nothing.
No magic happens along the way: the machine has to be on and online, and bypassPermissions by default means the agent runs tools without asking.