Guides
The fleet needs no API key.
Loom drives six real Claude Code CLI sessions, the official CLI from Anthropic, signed in with the Claude account you already have. If claude runs in your terminal, the fleet runs in Loom.
Setup
Sign in once, in your own terminal.
Loom does not wrap an API or ask you to mint a key. Install the official CLI, sign in the way Anthropic intended, and every fleet slot inherits that login. The CLI itself is documented at docs.claude.com.
# install the official Claude Code CLI
$ curl -fsSL https://claude.ai/install.sh | bash
# sign in with your existing Claude account
$ claude loginWhy it works this way
The real CLI, multiplied by six.
Official, not imitated
Every fleet slot is a genuine Claude Code session with its full TUI, the same behavior and updates you get in a bare terminal. You can click into any of the six and type.
No second bill
Loom is free and adds no account of its own. The fleet draws on whatever your Claude login already gives you, so there is no key to fund and no seat to buy.
Pooled accounts
Add more than one Claude account and Loom assigns them across the six slots. When one hits a usage limit, Loom parks it and rotates to the next so the mission keeps moving.
Common questions
Logins, answered.
What happens when I hit a usage limit?
Loom parks the limited account, rotates the slot to the next pooled account, and recovers the session. The mechanics are covered in Rate limits and Account rotation.
Do I need an API key for anything at all?
Only the Conductor, the model that plans and supervises, takes a key, and even that is optional: run it on a local model and there is no key anywhere. Setup lives in Bring your own key.
Does Loom take my Claude credentials?
Loom has no account system and no telemetry. Authentication belongs to the official CLI, the same sign-in flow you would use without Loom, and there is nothing to register for beyond the Claude login you already use.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.