Capabilities
Pick a repo. Everything follows.
Workspaces are Loom's authorized registry of the folders it may touch. Choose one and the file explorer, source control, and all six fleet sessions switch to it together.
One switch
The whole app changes context.
There is no per-panel setup and no session left pointing at the wrong folder. Switching workspace is one action, and every part of Loom moves with it.
The explorer
The file explorer re-roots to the workspace you picked, so what you browse is exactly what the fleet is working on.
Source control
The git panel follows along: staging, diffs, and the full git graph for that repo, ready for reviewing what the fleet shipped.
The fleet
All six Claude Code sessions run in the chosen workspace. One pick puts every terminal in the same repo, on the same job. See the fleet.
Authorization
An allow-list, not an open door.
Six parallel agents should not have the run of your disk. The workspace registry is the boundary: folders you have explicitly authorized, and nothing else.
Authorized or it does not happen
Every file, git, and shell operation is checked against the workspace authorization registry. Paths outside the registry are simply off limits.
Secrets stay out of reach
On top of the workspace checks, a secret-path deny-list blocks reads and writes to sensitive paths, so credentials are neither leaked nor overwritten.
Nothing phones home
No telemetry, no analytics, no account beyond your Claude login. The registry, like everything else, lives on your machine. See security.
Questions
Workspaces, answered.
Can I register more than one workspace?
Yes. The registry holds every folder you have authorized. Switching between them moves the explorer, the git panel, and all six sessions in one step, so jumping from one project to another takes seconds.
What if a session tries to leave the workspace?
It cannot. File, git, and shell operations are all checked against the registry, which keeps the fleet's work inside the folders you authorized.
Does this work the same on every platform?
Yes, on macOS, Linux, and Windows. On Windows, each terminal tab can additionally run its own WSL distro, so a workspace can live in Linux userspace too. See Loom with WSL.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.