TermLink
Open app
← All posts
4 min read

Running Claude Code on a Windows host (and why TermLink picks cmd.exe)

The Esc key is the one Claude Code cannot live without, and PowerShell eats it. Why the TermLink host defaults to cmd.exe on Windows, and what that means for your sessions.

TermLink hosts run on macOS, Linux, and Windows — a Windows workstation is a perfectly good machine to leave an agent working on, and you can check on it from a Mac, a phone, or a browser you have never signed into before.

There is one Windows-specific decision worth explaining, because if you did not know about it you would file it as a bug.

The host defaults to cmd.exe

Not PowerShell. The reason is a single key.

Claude Code draws a full-screen terminal UI, and that UI depends on Esc — it is how you cancel a prompt, back out of a menu, interrupt what the agent is doing. In PowerShell, PSReadLine (the line-editing module that gives you history and completion) intercepts the Esc key for its own purposes. The keystroke gets swallowed before it reaches the program you are running.

The result is an agent you cannot back out of. So the TermLink host opens cmd.exe by default, where Esc arrives where it is supposed to.

This is not a TermLink quirk — it is why terminal UIs in general behave strangely under PowerShell. TermLink just declines to ship the broken default.

You still have PowerShell

cmd.exe is the shell the session starts in. Type powershell and you are in it, like any other command. Run your build, do your thing.

The recommendation is narrow: run the interactive agent — the thing with the TUI and the Esc key — in the default shell, and treat PowerShell as one more program you can launch inside it.

The rest is the same

Everything else on Windows works the way it does anywhere else:

termlink login
termlink host

The machine registers under your Google account and dials out to the relay, so it sits happily behind a home router or a corporate firewall with no inbound port and no firewall exception to argue for. Start claude, flip Auto-Yes on, and go.

Reaching a Windows box from anything else

The client is a browser. A Mac, a Linux laptop, a phone, a machine at the office — open the web client, sign in, and the Windows host is in your list next to everything else. Mixed fleets are the normal case, not the exotic one: a Mac laptop, a Windows workstation, a Linux server, all in one list, each card showing what its agent last said.


Full walkthrough: getting started with TermLink.