Guides
Reaching your server
Mucq connects straight to your server. Tailscale is the easy way to make that work from anywhere; your own WireGuard or a public VPS work too.
On this page
Mucq opens a direct SSH connection from your device to the server's host and port. There's no service of ours to route through, no jump host and no ~/.ssh/config. So the one question is: can this device reach that host and port?
At home, on the same network, it usually can. From a café or a train, it needs a way in. Here are three, best first.
Tailscale (recommended)
Tailscale puts your devices and servers on one private network, wherever they are, with no ports open to the internet. Install it on the server and on your Mac, iPhone and iPad, sign them in to the same account, and use the server's Tailscale name or address as its Host in Mucq.
Mucq doesn't know or care that Tailscale is there. To Mucq it's simply a host that answers, from home and from the train alike. Tailscale is a separate service with its own account; it carries the connection, Mucq only connects through it.
Your own WireGuard
If you already run a WireGuard network, use it. Connect the device to it, and add the server by its address inside that network. Same idea as Tailscale, with you running the plumbing.
A public VPS
A VPS with a public address works as it is: Mucq connects to its name or IP. Then the server's SSH is open to the whole internet, so make it keys only, as in step 7 of Set up a Linux server. Never leave SSH on the open internet with password logins.
When the network changes
Mucq keeps an eye on the connection so you don't have to:
- A server that stops answering reads Offline in its header. Mucq checks it again every few seconds and whenever the network changes, and reconnects its terminals as soon as it answers.
- A silent connection is noticed within about a minute and a half, through SSH keepalives.
- When you come back to Mucq on iPhone or iPad, it checks every open connection at once. If one died while you were away, the last screen stays in place under Connecting to devbox… while Mucq reconnects, and tmux redraws it.
Your sessions don't depend on any of this. They live in tmux on the server, and Claude keeps working whether you're connected or not.