Guides
Most fixes are one command.
The fleet is six real Claude Code CLI sessions, so most problems are CLI problems with CLI fixes. Here is what to check when a pane misbehaves, and what Loom already fixed before you noticed.
The big two
No CLI, or no login.
If terminals report that claude cannot be found, the official CLI is not installed or not on your PATH. If panes keep asking you to sign in, the CLI has no login to reuse. Both have the same two-line cure, run once. Every session in the fleet reuses that login, with no API key needed, as the Claude login guide explains.
# install the official Claude Code CLI
$ curl -fsSL https://claude.ai/install.sh | bash
# sign in once; all six sessions reuse it
$ claudeAlready handled
What Loom fixes on its own.
Exited sessions
The watchdog relaunches a CLI that exits and re-sends its task after recovery, so a crashed pane is a blip in the activity strip, not a dead slot. See smart steering.
Stalls and drift
A session that goes quiet or wanders off-task gets nudged back. Loom watches every terminal so you do not have to babysit six of them.
Usage limits
Rate limits are recovered, and with pooled accounts the limited one is parked while the slot rotates to the next. Details on the rate limits page.
Symptoms
When something still looks wrong.
A pane shows no output
Check its activity strip first: the session may be thinking rather than stuck. If the CLI actually exited, the watchdog relaunches it and re-sends the task. Every pane is a real TUI, so you can also click in and type to it directly, and shift+tab cycles that terminal's permission mode if a prompt is what stopped it.
A terminal is waiting on a permission prompt
Auto-accept presses only the safe affirmative and it is toggleable, so check whether it is on for that pane. The permission modes guide covers the modes and the per-terminal shift+tab cycle.
Where do the logs live?
The terminals are the log. Each pane is a real PTY session, and the scrollback holds everything the CLI printed, searchable with the terminal's built-in search. The mission's activity strips record what each session was doing, and the source control panel shows exactly what changed on disk.
Loom cannot touch a file or repo I expect it to
Every file, git, and shell operation goes through the workspace authorization registry, and a secret-path deny-list blocks reads and writes to sensitive paths by design. Make sure the repo is an authorized workspace, and see the security page for what is intentionally off-limits.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.