Capabilities
A watchdog on every terminal.
Sessions drift, CLIs exit, limits land. Loom's watchdog nudges drifting sessions back on task, relaunches exited CLIs, and re-sends the task after recovery, so the mission you briefed is the mission that runs.
The watchdog
Three moves, applied automatically.
Nudge
A session that wanders off its task gets steered back to it. Drift is corrected the moment it appears, not discovered in a confusing diff hours later.
Relaunch
If a CLI exits, Loom relaunches it. An empty pane is a state to recover from, not a reason for a slot to sit dead for the rest of the night.
Re-send
After recovery, the task goes back out to the session. The slot returns to the work the mission assigned it, not to a blank prompt.
In practice
You can watch it happen.
The Conductor watches every terminal, and the mission DAG with live activity strips shows what each session is doing. When the watchdog steps in, you see what happened and what it did about it. These are real Claude Code TUIs, so you can also click into any terminal and steer by hand whenever you want.
# slot 2: output stalled
14:02 nudge sent, session back on task
# slot 5: CLI exited
14:11 relaunching claude
$ 14:12 task re-sent: migrate routes/billingWhy it matters
Long missions hold together.
Hours, not minutes
One stalled session quietly halves a two-slot mission. Across six slots and an overnight run, steering is the difference between waking up to results and waking up to five frozen panes.
Limits included
Recovery covers rate limits and stalls alike. On usage caps, Loom parks the limited account and rotates to the next one in the pool, then the task is re-sent.
Moving is not finished
Steering keeps sessions working. Whether the work actually counts is a separate question, and Loom answers it separately: verification re-checks every task before a slot is marked done.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.