LoomAiWindows · free while in beta
Write the steps in your own words. It does the rest.
LoomAi sits on top of Claude. You write down how a job should go, in ordinary sentences with no code in them: the steps in order, what each one hands over, and where it stops and asks you. Then it runs that, on your own machine, for as long as the work takes.
Windows 10 or 11 · 150 MB, unzip and run — there is no installer · checksum
- Work out how to build itDone8m 24s
- Write the code and the testsDone41m 06s
- Read it back against the planWaiting for you9m 37s
Everything you asked for is there, and it names the two places where it had to guess. Accept it, or send it back with what you want changed.
- Write the hand-overNext in line—
- and 5 more steps in this plan
Three plans, one tool. Each one is a page of sentences somebody wrote themselves. Press Accept and the next step starts without you.
Why it is different
Long work you can walk away from, and still answer for.
You write it, and you write it in your own language.
A plan is a page of sentences: do this, hand over that, stop here and ask me. If you can brief a colleague, you can write one — and you can change it afterwards without asking anyone.
Everything you already do with Claude, you can do here.
Stop a job halfway and pick it up tomorrow. Ask it what it is doing while it works. Have it lay out what it intends to do before it touches anything. And when it reaches a decision only you can make, it stops and asks you in plain words rather than guessing.
Nothing happens off the record.
Every decision, every refusal and every hand-off is written down as it happens, beside the files the work produced. You can go back and read how the work reached the shape it is in.
We never see your work.
Nothing you write and nothing you make reaches our servers. Your work stays on the computer you made it on. We cannot sell it, hand it over or train on it — we never have it.
How a run goes
Four things you do. The rest happens while you are elsewhere.
- 01
Write down how the job should go.
In ordinary sentences: the steps in order, what each one has to hand over, and where it must stop and ask you. No code, no diagrams, nothing to install. LoomAi comes with written plans you can start from and change.
- 02
Point it at the folder the work lives in.
Your files stay where they are. Claude runs on your own machine, signed in as you, reading the same folders you do.
- 03
Say what this particular job is.
The plan stays the same; the job changes each time. A page of notes, the email, the screenshots — whatever you would have sent a colleague.
- 04
Leave, and come back to something you can check.
It works for hours, asks when it needs you, and stops when the job is done or when it is out of its depth. Next week, run the same plan again without writing a thing.
Before you try it
What this needs from you, with nothing left out.
The beta is free, so there is nothing to talk you into. These are the six things that surprise people.
- A Claude subscription
LoomAi does not include Claude. You need your own Claude Pro or Max subscription, with Claude Code installed on your machine. You sign in on Claude's own page; LoomAi keeps that sign-in on your machine and hands it only to Claude Code. LoomAi runs entirely on your machine, so your sign-in, your files and anything you type are never sent to us — what Claude reads to do the work goes to Anthropic, under your own Claude account.
- Windows, for now
Windows 10 or 11. macOS and Linux come after the beta. The beta build is not signed yet, so Windows will warn you the first time you open it.
- A connection
Claude needs the internet to think, so LoomAi cannot work offline either.
- Rough edges
A beta build does not update itself, and each one expires on a set date. New builds are announced in the Discord. Report anything you run into in #bug-reports — that is what the beta is for.
- A little goes back
LoomAi sends us metadata only — when the app opens, when you save a plan and what kind of work it is, and when something breaks: the time, and which part of LoomAi stopped. The country each message came from is worked out from the address it arrived on, and the address itself is dropped at that moment. Never your files, never a plan's words, never anything you typed. The agreement LoomAi shows before it will open spells out every line of it. None of this can be switched off, because it is the only way we hear that LoomAi broke on a machine we cannot see. What goes back, in full.
- Folders and plans from others
A folder's own tools run. Whatever a folder sets up for Claude Code — its instructions, skills, hooks and MCP servers — runs whenever LoomAi works in it, as you. Claude Code asks whether you trust a folder first; in LoomAi, connecting the folder is that choice. What LoomAi limits is what each step of a plan may run. So a folder or a plan someone else gave you can run programs and send your files away: read it, or scan it with a security tool, before you connect it or run it.
Community
Everything is announced in one place.
New builds, known problems, what is being worked on next, and the people who can answer you — all in the Discord. Nothing is announced anywhere else.