How a new user creates a Loom Cloud account, what the sign-in and consent steps look like, and what you have when it finishes.
The fastest path is the command line: two commands install Loom and create your account. The website offers the same sign-in if you prefer a browser.
curl -fsSL https://loomcloud.ai/.well-known/cli/install.sh | sh
loom setupirm https://loomcloud.ai/.well-known/cli/install.ps1 | iex
loom setuploom setup walks you through these steps in order. If ~/.loom/stores.toml already holds your credentials for https://loomcloud.ai (from an earlier setup or loom login), the sign-in steps (2 to 5) are skipped and stores.toml is not rewritten: it prints Using your existing Loom stores for https://loomcloud.ai; run loom login to sign in again. and goes on to the harnesses.
Y, or type a comma-separated list of names to pick some.I agree. There is no flag that skips this. Only then does the service send a code; it answers "If that address can receive mail, a sign-in code is on its way", whether or not the address can receive mail. If you have asked for too many codes in a short time it says too many sign-in code requests for this address; wait a few minutes and run it again (exit status 2) and sends nothing.coding, loom_demo and kanban) are created; it does not finish until the last of them is ready. A single status check that times out is retried until the 120 seconds are up. If the server has no room for a new trial account, setup stops with loom login: Trial capacity is currently full. Please try again later. (exit status 2); try again later.~/.loom/stores.toml, installs or updates Loom in each selected harness, verifies each one, and prints a result table with any restarts needed.Automation can pass --harness codex (repeatable) and --json. The code is still read from a hidden prompt, never from arguments. See the CLI reference.
Go to <https://loomcloud.ai/> and choose Install or sign in. The site asks for your email, sends a one-time code or sign-in link, and then shows the install steps and your store definition at /stores. The two install actions shown there are the same two commands above.
While the stores are created the site shows a setup status page (Signed in as ..., "setting up your hosted store"). If it reports Trial capacity is currently full. Please try again later., wait and try again. If it reports Store setup hit a problem. Please try again or contact us., a Try again button appears below it; it asks for your consent again and re-runs the setup, which is safe to repeat.
Sign-up is open: anyone who can receive an email code and accepts the Terms and Privacy Policy gets an account.
Your account gets one organization with these stores:
| Store (section) | Domain | Purpose |
|---|---|---|
coding | CodingDomain | Your default project memory. Starts nearly empty. |
loom_demo | CodingDomain | A seeded, writable store for the tutorials. |
kanban | LogDomain | Multi-agent coordination board, already initialized. |
Setup sets default = "coding" and records each store's endpoint, store, server_key, store_key, namespace_scheme and web_origin in ~/.loom/stores.toml. See the stores.toml reference.
loom --version
loom list_storesThen open a new session in your agent and ask:
List my Loom stores and describe which store is the default.Continue with the quick start.
Install the CLI there and run loom login with the same email. It delivers your stores to that computer without installing anything into your harnesses. See Set up and sign in.
See Troubleshooting.