Install on Linux

1. Pick the right build

Builds exist for amd64 and arm64 — the second one covers a Raspberry Pi or an ARM cloud instance.

uname -m
# x86_64   → termlink-linux-amd64.tar.gz
# aarch64  → termlink-linux-arm64.tar.gz

Current URLs are on the download page.

2. Verify, unpack, install

Every release ships a SHA256SUMS file. On a machine you reached over SSH this is the cheapest sanity check available.

sha256sum termlink-linux-amd64.tar.gz
# compare with the line in SHA256SUMS

tar -xzf termlink-linux-amd64.tar.gz
chmod +x termlink
sudo mv termlink /usr/local/bin/

Nothing blocks the first run here — Linux has no equivalent of Gatekeeper or SmartScreen, so there is no unsigned-binary prompt to get past.

3. Sign in and share a terminal

termlink login     # opens Google sign-in
termlink           # share this terminal
termlink whoami    # which account am I on?

On a headless box, termlink login still needs a browser to complete Google sign-in — follow the URL it prints from whatever machine you are sitting at.

To share a terminal that already has Claude Code running in it, use termlink claude instead.

4. Keeping it up after you log out

This is the step people skip on a remote server. TermLink runs in the terminal you started it in. Close the SSH session and the process goes with it, and the machine shows as offline.

tmux new -s termlink
termlink
# Ctrl-b d to detach; the session keeps running

screen works the same way. There is deliberately no daemon mode: nothing is installed as a service, so nothing is left behind when you delete the binary.

Outbound only

The machine dials out over HTTPS and never accepts an inbound connection, so there is no firewall rule to add and no port to forward. A network that blocks outbound 443 will stop it — how that works.