Repository navigation
Windows support (native, or a documented WSL2 setup) #9
Description
What you're trying to do
We use Claude Code natively on Windows 11 and would like to follow and steer our sessions from a phone or a voice call with Sesame Link, the way it works on macOS.
Today this isn't possible:
- The installer is a
curl … | shscript, and the docs list builds for macOS (signed) and Linux (preview). There is no Windows build. - Claude Code sessions need tmux 3.4 or newer, which doesn't exist natively on Windows.
The only route we found is WSL2, and in practice it means running a second, separate Claude Code:
- a Linux distribution to install and maintain (we only have Docker Desktop's internal
docker-desktopdistro, so we'd start from scratch, and tmux 3.4 rules out Ubuntu 22.04); - a separate
~/.claudeinside WSL, so our Windows settings,CLAUDE.md, skills, plugins, history and login don't carry over; - the code stays on the Windows drive, reached through
/mnt/c, which is slow from WSL; - sessions started on Windows stay invisible to Link.
That was too much setup to try, so we stopped there.
What would help
From the user's side, roughly in order of effort:
- Say whether WSL2 is supported today. If it is, a short docs page would already help: which distribution to use, how to keep Link running when no terminal is open (the troubleshooting page mentions
loginctl enable-lingeron Linux; does WSL keep the distribution running too?), and how it behaves with code under/mnt/c. - Native Windows support:
- install from PowerShell or winget, with a signed binary;
sesame-link claudeworking from PowerShell or Windows Terminal, with the Windowsclaudeand the Windows~/.claude;- sessions that keep running after the terminal window is closed, with a way to attach to them again (the Windows counterpart of tmux detach/attach);
- Link starting at sign-in, with a tray icon in place of the macOS menu-bar app;
/open-sesameworking in a native Windows Claude Code session.
If this belongs in an RFC instead, let us know.
Area
CLI
Environment
- Windows 11 (build 26300), x64
- Claude Code 2.1.310, native Windows install
- WSL 3.0.3, no Linux distribution other than
docker-desktop - Sesame Link: not installed (no Windows build)
Activity
BluFinSolutions commentedon Oct 26, 2026
Anyone?
darkmirage commentedon Oct 26, 2026
Hi, we are investigating this possibility right now. Unfortunately, the lack of a fully supported equivalent to tmux has been a barrier to this. One possible option here is to give up on the ability to concurrently view the session the native TUI while the agent is working on it, but this has been an important design goal of this project.
There are some possible paths we are exploring. Appreciate your patience.
BluFinSolutions commentedon Oct 26, 2026
Thanks for the quick and candid reply, and for looking into it. Keeping the native TUI viewable while the agent works makes sense as a design goal, so here's some input from the Windows side in case it helps.
On the trade-off. For us the main value of Link is reaching sessions when we're away from the PC, from a phone or a voice call. While we're at the desk, we rarely need to watch the native TUI and steer remotely at the same time. A first Windows release without concurrent viewing (for example, the local terminal re-attaches when you're back) would already cover most of our use. If it shipped as an opt-in preview, macOS and Linux could keep the full design while Windows catches up.
Possible tmux stand-ins (you may well have looked at these already; we haven't tested either with Link):
.tmux.confand installs with winget. Its README says Claude Code's agent teams already open teammates in psmux panes, which suggests Claude Code's own tmux integration works with it.wezterm cli spawn,send-textandget-textoffer a scripting surface close to tmux's.Happy to try a Windows preview build on Windows 11 x64 and report back.