Troubleshooting

TermLink is not a background service. It runs in the terminal you started it in, so it goes away when that terminal does — you closed the window, the SSH session ended, the laptop slept, or the machine rebooted.

1. Go to the machine itself.
2. Run termlink again in a terminal there.
3. Leave that terminal open. To keep it alive after you disconnect from SSH, start it inside tmux or screen.

If the machine is on and you did leave TermLink running, check that it can reach the internet outbound over HTTPS. TermLink only makes outgoing connections, so a firewall that blocks outbound 443 will stop it — but nothing needs an inbound port opened.

Your session is not lost while this is on screen. The terminal is still running on your machine; what dropped is the pipe between your browser and it. When it reconnects, the screen is repainted as the session left it.

If it stays on Reconnecting… for more than a minute, the machine itself has probably gone offline rather than the browser — see above.

Reload the page first. If it persists, sign out and back in — the usual cause is a session that expired while the tab was open.

The TermLink host uses cmd.exe by default for exactly this reason. If you have changed the shell, or you are running the agent inside PowerShell yourself, Esc stops reaching the application.

The fix is to run the agent under cmd.exe. Why that default exists, and what else differs on Windows, is in running Claude Code on Windows.

The commands that exist:

termlink            Share this terminal (default)
termlink claude     Share this terminal with Claude Code already running
termlink client     Connect to one of your terminals from the CLI
termlink login      Sign in with Google
termlink logout     Sign out
termlink whoami     Show the signed-in account
termlink devices    List or sign out the machines on this account
termlink update     Update to the latest version
termlink help       Show this help

The one people miss is the first line: to share a terminal you run termlink on its own. There is no subcommand for it.

Run termlink help for the command list. termlink devices is the exception that does take options:

termlink devices -revoke <id>   sign out one machine by id
termlink devices -revoke-all    sign out every machine, including this one

To switch accounts, run termlink logout first. To see which account you are on without changing anything, use termlink whoami.

The cap counts sessions, not viewers — you can watch the same sessions from as many browsers and phones as you like without using any of it up. Closing a session frees a slot immediately.

What each plan includes is on the pricing page.

Auto-Yes is the per-session toggle for this. It confirms permission prompts so a long run keeps going while you are somewhere else, and you can flip it from a phone. It is off by default and it is a convenience rather than a safety feature — how it works, and when to leave it off.

If the session is gone rather than blocked, the host process stopped. That is the first case on this page.