Capabilities
Rotate past the limit.
Pool more than one Claude account and Loom assigns them round-robin across the six slots. When an account hits its usage limit, Loom parks it and rotates to the next one. The mission keeps moving.
How it works
Round-robin across six slots.
Every slot in the fleet takes an account from the pool in turn. When a usage limit lands, the affected account is parked instead of being retried into the same wall, and the slot rotates to the next account in the pool. Pooled accounts and rate-limit rotation shipped in Loom v0.7.4.
# three pooled accounts, six slots, round-robin
account A -> slots 1, 4
account B -> slots 2, 5
account C -> slots 3, 6
# account B hits its usage limit
$ park B, rotate its slots to the poolThe foundation
Built on your Claude login.
No API key for the fleet
The six sessions are real Claude Code CLIs running on your existing Claude login. Nothing to provision and no per-token bill for the fleet.
Parked, not hammered
A limited account is set aside rather than retried against the same cap. Loom treats the limit as a signal, not an error to fight.
Rotation is automatic
The slot picks up the next account in the pool and the mission continues. You do not have to notice that a limit ever happened.
Questions
Common questions.
Do I need multiple accounts?
No. Loom runs the full fleet on a single Claude login. Rotation becomes useful the moment you add a second account to the pool, especially for long missions and overnight runs.
Do I need an API key for the fleet?
No. The fleet uses the official Claude Code CLI and your existing Claude login. The only key you bring is for the Conductor, the reasoning model that plans and dispatches.
What happens when an account is parked?
Loom rotates the slot to the next account in the pool and carries on. Recovering from rate limits is part of how Loom steers the fleet, so a parked account asks nothing of you.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.