A session manager for AI coding agents
Your agents run on your own machines. TermLink puts them in one list you can open from any browser or phone — no SSH, no VPN, no open ports.
What is an AI coding agent session manager?
It is the place your running agents live, separate from the machine you happen to be sitting at. An agent works inside a terminal on some computer; a session manager keeps that terminal reachable, keeps several of them side by side, and tells you which one is waiting on you.
That last part is the one that matters once you are running more than one. Reaching a machine is a solved problem. Knowing which of your agents needs a human right now is not.
Which coding agents does TermLink work with?
What you connect to is the real terminal on your machine, so a coding agent that runs in a terminal runs here. TermLink recognises Claude Code, Codex CLI, and Cursor Agent specifically — it reads each one's own approval prompt.
Claude Code is the agent we support most closely and test the most. Codex CLI and Cursor Agent are both in daily use here — what recognising an agent actually buys you is set out on Codex CLI remote access.
Because the session is a real terminal and not an agent-shaped wrapper, the same window works for everything else you would do in one — running the test suite, reading a log, checking out a branch.
How do I manage multiple coding agents at once?
Every machine you register shows up as a card in one list, and each card carries that session's most recent message from the agent. One line each. You read four lines and go to the one that needs you.
The machines do not have to be alike — a laptop, a workstation, and a box that exists only to run agents all sit in the same list. Neither do the agents: Claude Code on one, Codex on another.
Running several Claude Code agents at once, across machines walks through what that looks like in practice.
How does a remote AI coding agent work here?
The agent is never remote from your code — it is remote from you. It runs on the machine your repository is already checked out on, with your tools and your environment, and what travels to your browser is the terminal it is working in.
You run one command on that machine and it registers under your Google account by dialing out. From then on you open a remote coding agent terminal from any browser and you are looking at the real one, repainted as the agent left it.
The machine never accepts inbound connections, so there is no SSH port to expose, no key to distribute, and no VPN to dial into. See running Claude Code on a remote machine.
This is also the part people get wrong when comparing tools: hosted services run the agent on their infrastructure instead, which is a different trade — where that line falls.
Does the agent keep running when I close the browser?
Yes. The session lives in a terminal on your machine, not in the browser tab, so closing the tab does not interrupt the agent. Reconnect and the screen is repainted exactly as the agent left it, TUI and all.
The one requirement is that the host process keeps running. TermLink is not a background daemon like tmux — if you close the terminal the host is running in, the machine goes offline until you start it again.
Can I stop the agent asking permission on every command?
Turn on Auto-Yes. TermLink watches the session for the agent's permission prompt and confirms it, so a long run does not sit blocked while you are away. It reads Claude Code's numbered menu, and Codex and Cursor's own approval prompts too.
It is a per-session toggle and it is off by default. Treat it as a convenience rather than a safety feature — how Auto-Yes works, and when to leave it off.
Does it work from a phone?
Yes. TermLink runs in a mobile browser and adds a control-key row — Esc, Tab, Ctrl+C, arrows — so a terminal UI is usable on touch. You can read what the agent is doing and answer its prompts.
You can also drop a screenshot onto the terminal: TermLink uploads it to the host machine and types the saved path in for your next prompt. See using Claude Code from your phone.
Which operating systems can host an agent?
macOS, Linux, and Windows. The client is 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 rely on — why that choice, and what it means.
Will it tell me when an agent needs me?
Not by notification — there is no push, email, or browser notification today. What you get instead is the list: each machine card shows that session's latest message, so a glance tells you which agent is working and which is waiting.
What does it cost?
There is a free plan. Free and Pro differ in exactly one thing — how many sessions run at the same time. Free gives you two, Pro gives you eight at $9 a month.
The cap counts sessions, not viewers: you can watch them from as many browsers and phones as you like. Every active session streams live with no time limit on either plan.
Register the machine your code lives on, and open its session from anywhere.