Guides
Linux userspace, Windows desktop.
Loom is a native Windows app, but any terminal tab can open straight into a WSL distro. Run the whole fleet inside Linux without leaving your desktop.
Per-tab distros
Every tab picks its own world.
One window, many userspaces
WSL is chosen per tab, not per app. Open Ubuntu in one tab and pwsh in the next, side by side in the same window, and point each pane at whichever userspace the work needs. The tabs and splits guide covers the layout moves.
Your real login shell
A WSL tab launches the distro's own login shell, with shell integration for zsh, bash, and fish. Your dotfiles, your prompt, and your tools behave exactly as they do in a bare console.
Native PTYs underneath
Each WSL tab is a real pseudo console feeding Loom's WebGL terminal, so true color, scrollback search, splits, and background streaming all apply inside Linux too.
The fleet in Linux
Put the sessions where the code lives.
If your project lives in WSL, the fleet should too. Install the official Claude Code CLI inside the distro and sign in once. Fleet sessions running in WSL tabs then build with your Linux toolchain, against Linux paths, with no translation layer in between.
# inside any WSL tab, install the Claude Code CLI
$ curl -fsSL https://claude.ai/install.sh | bash
# sign in once; sessions in this distro reuse it
$ claudeDetails
WSL, answered.
Do I need a separate Linux build of Loom?
No. The native Windows installer, around 13 MB, includes per-tab WSL. Loom stays a Windows app while your shells, your builds, and your fleet sessions live in Linux. The Windows page covers the rest of the platform story.
Can host and WSL tabs mix in one window?
Yes. Tabs and splits do not care which side of the boundary a pane is on, so a WSL terminal can sit next to a pwsh terminal, an editor, and a web preview in the same layout.
Which shells get integration?
zsh, bash, and fish get full shell integration inside WSL. Anything else still works, it just spawns as a plain login shell without the extras.
Does my Claude login carry over from Windows?
The CLI inside the distro keeps its own login, so sign in once there with claude. After that, every fleet session you run in that distro reuses it, the same way the Claude login works on the host.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.