LoomFlow

Lightweight AI-native workflow builder for individuals and small teams, describe your idea in natural language, get a runnable workflow on a visual canvas, publish it as an API. One-command Docker self-hosting. Open-source alternative to Dify / n8n.

Runs with mockssource: GitHubhomepageTypeScriptMITcommit 2c9dfe0bca4b

TypeScript, MIT licensed. The project labels itself: ai, ai agent, ai agents, llm, low code, nextjs, self hosted and supabase.

LoomFlow runs, with stand-ins for the services it depends on. An Argusic agent installed it in 12 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Install completes, Next.js dev server starts on port 5000 and returns 200 on /api/health, and the full test suite of 765 tests across 68 files passes cleanly.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
1
last tested
stars
139
forks
8
open issues
3
watchers
0
size
12 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing LoomFlow, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js v18 does not support `node:util` `styleText` export required by Vitest 4.x5 minutes
Install time
12 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
pnpm test exited 0, 765 passed across 68 test files; curl http://localhost:5000/api/health returned HTTP 200 with {"status":"ok","service":"loomflow","version":"v0.1.11","db":"error: TypeError: fetch failed"}
Model tokens used
57,247
Exact commit tested
2c9dfe0bca4b
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

[[email protected]] injecting env (0) from .env.local -- tip: 👥 sync secrets across teammates & machin…
{"status":"ok","service":"loomflow","version":"v0.1.11","db":"error: TypeError: fetch failed","time…
The server is up and responds with HTTP 200 on `/api/health`. The DB shows "error: fetch failed" si…
exec
/bin/sh -lc 'cd /work/repo && pkill -f "tsx.*src/server.ts" 2>/dev/null; mv .npmrc.bak .npmrc 2>/de…
 exited 143 in 0ms:
Here's the full run report.
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":12,"errors"…
tokens used
57,247
Here's the full run report.
**ARGUSIC_RESULT:** {"install_succeeded":true,"launch_succeeded":true,"install_minutes":12,"errors"…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 12 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 237 ai projects Argusic has installed and timed, LoomFlow was the 180th fastest to reach a running state, and 168 of 237 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.04

Topics (from GitHub)

aiai-agentai-agentsllmlow-codenextjsself-hostedsupabasetypescriptworkflowworkflow-automation

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/LoomFlow.svg)](https://argusic.com/subject/loomflow)

Questions

Does LoomFlow run?
LoomFlow runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 12 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test LoomFlow?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2c9dfe0bca4b. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test LoomFlow?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does LoomFlow take to install?
12 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does LoomFlow need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing LoomFlow?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does LoomFlow compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, LoomFlow was the 180th fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for LoomFlow?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion