Guides
Hit the cap. Keep the mission.
Six parallel Claude Code sessions will meet usage limits sooner than one. Loom treats a limit as a signal to route around, not an error to fight, so the mission keeps moving while you do something else.
What happens
Park, rotate, recover.
Park
When an account hits its usage limit, Loom sets it aside instead of retrying it into the same wall. No pane spins on a cap, and no slot wastes attempts that cannot land.
Rotate
With more than one Claude account in the pool, the affected slots pick up the next account round-robin and carry on. Rotation is automatic, so you do not have to notice the limit happened.
Recover
Rate limits and stalls are part of what Loom watches for across every terminal. Recovered sessions get their tasks re-sent, and work is still verified before it counts as done.
Pooling more than one account
The fleet runs on your existing Claude login through the official CLI, with no API key and no per-token bill, as covered in the Claude login guide. Add a second or third account and Loom assigns them round-robin across the six slots, so a single account's cap stops being the ceiling on a long mission. Pooled accounts and rate-limit rotation shipped in Loom v0.7.4, and the account rotation page shows the slot-by-slot mechanics.
One account still works
A pool is an optimization, not a requirement. On a single login, Loom still detects the limit, parks the account rather than hammering the cap, and recovers the affected sessions so the mission resumes rather than restarts. The mission DAG and live activity strips show exactly which tasks are waiting and which are still moving.
Why this matters most at night
A rate limit at 2 a.m. is the difference between waking up to a finished mission and waking up to five stalled terminals. Parking, rotation, and recovery are the same machinery that makes overnight runs dependable: brief before bed, review diffs over coffee.
Questions
Common questions.
Does rotation cost anything?
Loom is free and open source, and the fleet needs no API key. You pay your providers directly: your Claude plan covers the fleet, and your own key covers the Conductor. The pricing page lays it out.
Do I lose work when a limit hits?
No. The limited account is parked, the slot rotates or recovers, and the task is re-sent. Because Loom verifies work before it counts, a task interrupted mid-flight is finished and checked, not silently marked done.
Can I see when a limit happened?
Yes. Every pane is a real Claude Code terminal, so the limit appears in that session's scrollback, and the live activity strips show what each slot is doing at any moment.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.