TermLink docs
TermLink is one binary you run on the machine your code lives on. These pages cover getting it there, what the commands do, and what to check when something is not working.
Start here
Download
One archive per platform, containing a single executable. No installer, no service, no dependencies.
Getting started
Install, sign in, and open your first session from a browser — about two minutes end to end.
Install
The binary is not code-signed, so macOS and Windows both stop the first run. Each page says exactly what you will see and how to get past it.
macOS
Apple Silicon and Intel. Getting past Gatekeeper on an unsigned binary, and where to put it on
PATH.Linux
amd64 and arm64. No package manager and no daemon — plus keeping it running after you close an SSH session.
Windows
amd64 and arm64. The SmartScreen warning, and why the host uses
cmd.exerather than PowerShell.
When something is wrong
Troubleshooting
What each message on screen means —
Hosts are offline,Reconnecting…,unknown command— and what to do about it. Also the Windows Esc key problem.
Reference
CLI reference
Every command and what it prints —
termlink,claude,client,devices,update.Sessions and limits
What counts as a session, how many run at once, and what happens when the host process stops.
Auto-Yes
Which prompts it answers, the key it sends per agent, and the default new sessions inherit.
How it works
Connecting without SSH or a VPN
Your machine dials out to the relay and never accepts an inbound connection, which is why there is no port to open.
Security
What the relay can and cannot see, including the parts that are not encrypted end to end.
Plans and session limits
Free and Pro differ in one number: how many sessions run at the same time. The cap counts sessions, not viewers.
Platform notes
Running on Windows
Why the host uses
cmd.exeby default, and what that means for terminal UIs that rely on the Esc key.From a phone
The control-key row, and dropping a screenshot onto the terminal.
Something missing from these pages?
These are new and they are shorter than they will be. If you hit something that is not written down here, tell us what you saw on screen and it gets added — bert@n2computing.com.
