Find answers to common questions or get in touch
TermAway lets you access your Mac's terminal from your iPad, iPhone, or any browser on your local network. Here's how to get up and running:
http://192.168.1.x:3000).TermAway's server also runs on Linux. Here's how to set it up:
.tar.gz from the downloads page.tar xzf TermAway-Linux-*.tar.gz && cd termaway-linux && sudo ./install.shsudo systemctl start termaway. The server starts on port 3000 by default.http://your-linux-ip:3000 in any browser on the same network.On your own Wi-Fi, TermAway works out of the box. To reach it from anywhere (a coffee shop, your phone on cellular), add Tailscale: a free private network (WireGuard) across the devices in your tailnet. TermAway itself stays on your Mac; nothing runs in a TermAway cloud. Tailscale connects your devices directly when it can, and relays end-to-end encrypted traffic through its own servers when a direct path isn't available. It cannot read that traffic.
Tailscale: http://100.x.x.x:3000 entry next to your LAN URL. Click to copy it.Because your terminal is now reachable across your tailnet, set a password in the menu bar app so only you can connect.
By default a session lives inside the TermAway server: stop the server, or restart your Mac, and the shells inside it end. Turn on persistence and each session runs inside tmux instead, so your work keeps running and TermAway reattaches to it the next time it starts.
brew install tmux. TermAway won't let you turn persistence on without it.One thing to expect: TermAway replays a session's recent output when you reconnect, and that buffer lives in the server, so it starts empty after a restart. Your processes and tmux's own history survive — you reattach to a live screen, not to a log of what happened before.
Switching persistence back off asks what to do with sessions tmux is still holding, so nothing is left running where you can't see it.
Only if you ask them to. Turn on Keep sessions running when the server stops in Preferences → Server and each session runs inside tmux, so stopping the server — or rebooting — leaves your work running. It needs tmux installed. See the section above.
On your own Wi-Fi, no — TermAway runs entirely over your local network, with no internet or TermAway account required. To reach it from outside your network, add Tailscale (see above); traffic then flows over Tailscale's end-to-end encrypted network, with no TermAway cloud service in between.
TermAway is self-hosted, so your terminal data never passes through infrastructure we operate. Over Tailscale it's end-to-end encrypted (WireGuard); on your LAN you can enable TLS. You can set a password for server access, and TermAway is open source, so you can inspect the code yourself.
Make sure both devices are on the same Wi-Fi network, or both signed into Tailscale. Auto-discovery works on your LAN; over Tailscale, enter the Tailscale URL manually from the macOS menu bar app. Also check that your Mac's firewall isn't blocking incoming connections on the server port.
Try detaching and reattaching the session, or creating a new session. If the server has restarted, existing sessions may have been cleared. You can also restart the server from the macOS menu bar app.
TermAway uses your system's default shell (set in $SHELL). This is typically zsh on macOS and bash on Linux. Fish and other shells work as well — just change your default shell in System Settings (macOS) or via chsh.
Yes. TermAway's server runs on any Linux distribution with Node.js 18+. Download the Linux package from the downloads page and run the install script. The server runs as a systemd service and starts automatically on boot.
Yes, with Tailscale. No port forwarding or public TermAway URL is required: Tailscale reaches it over your tailnet's end-to-end encrypted network. See "Access from anywhere with Tailscale" above.
If you've found a bug or have a feature request, please open an issue on our GitHub Issues page. When reporting a bug, include:
If you need help or have questions that aren't covered here, you can reach us through: