Loom: the first principle AI agent.
Intuitive: no new syntax to learn. Productive: it writes and runs real code, and finishes the task instead of describing it.
Free to use · bring your own model provider
What it is like to use
Seven things about Loom, in the words the person who builds it uses for them. Nothing here is a number yet: the measurements behind these words are not published. When they are, they will be here.
Installing an MCP takes effect where you are standing, with no restart, and compaction is not something you sit and wait for.
It maintains its own library: the trap a run hit, the endpoint that had moved, the recipe that worked, written down and read back by the next run.
A very high cache hit rate. The long part of a conversation - the instructions, the files, the history - comes back from the provider's prompt cache instead of being worked out again every turn.
Agents open agents. A parent hands a job to a child, and several tasks move at once instead of one at a time in a single queue.
Programming work, end to end: it writes and runs real code, drives a real browser, and finishes the task instead of describing it.
You reach a running session from the browser, from another machine, or from your phone over the network - a long job does not tie you to one desk.
An agent is not limited to text and pictures: it can mount a real page into the conversation - buttons, forms, a board, an editor, or this page you are reading.
Install
Not published yet. The Homebrew tap has not been created and the first release is not out, so neither command below runs today. They are here to show where they will go, and every entry on this page says so instead of pointing at a file that is not there.
brew tap loombot/tap brew install loomcoming
Or in one line, which taps and installs in a single go:
brew install loombot/tap/loom
loombot/tap is the repository the formula will live in — it is not
created yet, so the name is a promise rather than a place.