Your Claude Code sessions.
From any browser.

Yes. Run `termlink host` on any machine — a workstation, a cloud box, a home server — and it registers under your Google account by dialing out to the TermLink relay. You then open TermLink in a browser and run `claude` there. The machine never accepts inbound connections, so you do not open an SSH port or set up a VPN.

Yes. The session lives in a terminal on your own machine, not in the browser tab, so closing the tab does not interrupt the agent. Reconnect and TermLink repaints the screen exactly as Claude left it. The one requirement is that the `termlink host` process keeps running — TermLink is not a background daemon like tmux.

Open TermLink from wherever you are. Each machine you registered is one line showing that session’s most recent message from the agent, so you can tell at a glance whether it finished, is still working, or stopped on a question. Tap the one you care about and you are in its terminal, at the point it actually reached.

Yes. The session belongs to the machine it runs on, not to the terminal or the app that opened it. Start it on a laptop, close the lid, and open that same session on a phone. You get the screen as the agent left it rather than a fresh one. You can also have it open in more than one place at once, because the plan cap counts sessions rather than viewers.

Turn on Auto-Yes. TermLink watches the session for Claude’s numbered permission menu — the one with `1. Yes` and a `No` option — and confirms the highlighted choice, so a long run does not sit blocked while you are away. It is a per-session toggle and it is off by default.

Treat it as a convenience, not a safety feature. Auto-Yes confirms whichever option is highlighted on a Yes/No prompt, which is normally Yes — it does not read the command and decide whether it is a good idea. Free-form questions are left alone. Leave it on for a run you trust; keep it off when Claude is doing something you would not want auto-confirmed.

Yes. TermLink runs in a mobile browser and adds a control-key row (Esc, Tab, Ctrl+C, arrow keys) so a terminal UI is usable on touch. You can read what the agent is doing, answer its prompts, and drop a screenshot onto the terminal — TermLink uploads it to the host and types the saved path in for your next prompt.

Remote desktop tools stream an entire screen: heavy, clumsy on a phone, and they need the far machine unlocked. SSH means an exposed port and keys to manage. TermLink hosts dial out and mirror only the terminal your agent lives in. Unlike tmux it is not a background daemon, but it adds what tmux does not have: a browser and phone client, a correct TUI repaint across reconnects, several machines in one list, and Auto-Yes.

Yes. What you connect to is the real terminal on your machine, so an agent that runs in a terminal runs here. TermLink also recognises Codex CLI and Cursor Agent specifically — it reads each one’s own approval prompt, so Auto-Yes answers them the way it answers Claude Code’s numbered menu. Claude Code is the agent we support most closely and test the most; Codex and Cursor are both in daily use here. There is more on this in the session manager for AI coding agents.

Claude Code Remote Control lets you reach a Claude Code session on your machine from another device. TermLink is built around a different job: keeping several machines in one list, in a full terminal, from a browser or phone. You register each machine once with `termlink host`, and every session you open is the real terminal — so the same window works for whatever else you run in it, not only for the agent. If you work on one machine and want the shortest path to it, Remote Control is a fine answer. If your work is spread across a laptop, a workstation, and a box that only runs agents, that is the case TermLink was built for. There is a fuller comparison of TermLink vs Claude Code Remote Control on its own page.

Yes. The host runs on macOS, Linux, and Windows, and TermLink runs in any modern browser, including mobile. On Windows the host uses cmd.exe by default because PowerShell’s PSReadLine swallows the Esc key that terminal UIs like Claude Code rely on.

Not yet — TermLink has no push, browser, or email notifications today. What it gives you instead is a glanceable list: each machine card shows that session’s latest Claude message, so you can see which agent is still working and which one is waiting on you.

Yes, there is a Free plan: Google sign-in, connecting to your own machines, real-time terminal access, and Auto-Yes. The plans differ in exactly one thing — how many sessions you can keep active at the same time. Free gives you two, Pro gives you eight, and in both cases every active session streams live with no time limit and no reconnect wait. The cap counts sessions, not viewers: you can watch them from as many browsers and phones as you like. Pro is $9 per month and adds priority support.