Blog
Limits are weather.
A long mission will meet a usage limit eventually. The interesting question is what happens in the next sixty seconds.
Six sessions, one allowance
Loom drives six real Claude Code sessions in parallel on your existing Claude login. That is the whole point, and it is also the math problem: six sessions draw on an account's usage allowance faster than one ever would. On a short mission you may never notice. On an overnight run, you will.
The default answer in most tools is to stall. The terminal prints a limit message, the session sits, and the mission quietly dies until someone checks in the morning. We think a usage limit should be treated like weather: expected, survivable, and not worth waking anyone up for.
So Loom lets you pool more than one Claude account. Accounts are assigned round-robin across the six slots, and the moment a limit lands, the affected account is parked until its reset instead of being retried into the same wall. Pooled accounts and rotation shipped in v0.7.4, and the rate limits guide covers the setup.
Mid-mission
Rotation is a relaunch plus a memory.
The detail that makes rotation actually work is the re-send. Swapping accounts means relaunching the CLI in that slot, and a fresh session knows nothing about the task it inherited. So after the rotation, Loom re-sends the task to the new session, the same way it re-sends work after a stall or a crash. The slot picks up where the parked account stopped, and the mission DAG never records the interruption as anything more than a pause.
# a usage limit lands during a mission
14:02 limit detected on account B
14:02 park B until its reset
14:02 rotate slot 4 to account C
14:03 relaunch CLI, re-send the task
# mission continues, B returns after resetThe rules
Three rules of the pool.
Round-robin by default
Slots take accounts from the pool in turn, so no single account carries the whole fleet while the others idle. Spread the load and the limits arrive later.
Parked, not hammered
A limited account is set aside until its reset. Retrying against a cap burns time and goodwill. Loom treats the limit as a signal, not an error to fight.
Nothing is dropped
Rotation re-sends the task, so the work assigned to a slot survives the account swap. You should not be able to tell from the finished mission that a limit ever happened.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.