TermLink

TermLink docs

You work in a browser tab: every machine you have registered is a card in one list, and clicking one puts you in its real terminal. Getting a machine into that list is one command on the machine itself.

npm install -g @termlink/cli
termlink login && cd ~/work && termlink start
                    # then open it from any browser

Start here

  • Getting started

    Sign in, register a machine, and open its session in a browser — about two minutes end to end.

  • Working in the browser

    What a session is, how the list works, what survives closing the tab, and sharing one with someone else.

  • Auto-Yes

    The toggle that answers an agent's permission prompts while you are away — and the default new sessions inherit.

Getting a machine connected

One npm package per machine you want to reach. Nothing to install on the device you are looking from — that is any browser.

  • Install

    npm install -g @termlink/cli. Requires Node.js 22 or later. No installer, no service, no separate download.

Install

The command is the same everywhere — npm install -g @termlink/cli. Each page below covers the Node.js prerequisite and platform-specific notes.

  • macOS

    Apple Silicon and Intel — npm picks the right build. Getting Node.js 22+ with Homebrew or nvm.

  • Linux

    amd64 and arm64. No package manager beyond npm and no daemon — plus keeping it running after you close an SSH session.

  • Windows

    amd64 and arm64, and why the host uses cmd.exe rather 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.

Command line

You do not need any of this to use TermLink — it is here for the machine side, and for reaching a session from another terminal rather than a browser.

  • CLI reference

    Every command and what it prints — start, login, whoami, devices, help.

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, Pro and Max 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.exe by 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.