Does illa-builder run?

Argusic could not verify that illa-builder runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 7 errors on the way, and recorded the session.

How did Argusic test illa-builder?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit a468660903e2. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test illa-builder?

The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does illa-builder take to install?

3 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 illa-builder need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing illa-builder?

7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for illa-builder?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

illa-builder

Low-code platform allows you to build business apps, enables you to quickly create internal tools such as dashboard, crud app, admin panel, crm, cms, etc. Supports PostgreSQL, MySQL, Supabase, GraphQL, MongoDB, MSSQL, Rest API, Hugging Face, Redis, etc. Automate workflows with schedule or webhook. Open source Retool.

Could not verifysource: GitHubTypeScriptApache-2.0commit a468660903e2

TypeScript, Apache-2.0 licensed. The project labels itself: aiagent, app builder, crud application, developer tool, developer tools, gui, hacktoberfest and internal development.

Argusic could not get illa-builder running. An Argusic agent installed it in 3 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

ILLA Builder and ILLA Cloud FE build successfully. Both Vite dev servers start and serve HTTP 200. Built dist/index.html includes bundled JS entry point.
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 80 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 80 / 100
cost of the verifying run: $0.07 (measured)
recorded runs: 2
last tested: 2026-09-26
stars: 12,323
forks: 1,208
open issues: 43
watchers: 96
size: 52 MB
created: 2022-04-18
last push: 2026-05-27

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-26. 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 illa-builder, 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.

OOM (exit 137) during chunk rendering2 minutes
pnpm lockfileVersion 6.0 incompatible with pnpm 12.x1 minute
pnpm blocks build scripts by default1 minute
Missing locale files at apps/builder/src/i18n/locale/1 minute
@uiw/codemirror-theme-github/src subpath import not resolved1 minute
[email protected] does not export named 'hsv'1 minute

Install time: 3 minutes
Cold machine to finish: 13 minutes
Errors hit and fixed: 7 hit, 7 fixed with no human help
How the result was proved: Dev server on port 3456 returned HTTP 200; 'vite build --mode self' completed successfully (9683 modules, all chunks written to dist/); cloud FE built on port 3457 also HTTP 200
Model tokens used: 345,242
Exact commit tested: a468660903e2
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
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

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

- `illa-cloud-fe` dev server on port 3457 → HTTP 200
- `vite build --mode self` for `illa-builder` → ✓ 11,088 kB main JS built
- `vite build` for `illa-cloud-fe` → ✓ built in 15.86s
- No unit tests in repo; Playwright E2E tests require a running backend (not available
exec
/bin/sh -lc "cat <<'EOF'
EOF" in /work/repo
 succeeded in 0ms:
Done. The ARGUSIC_RESULT line is printed above with all findings captured.
tokens used
345,242
Done. The ARGUSIC_RESULT line is printed above with all findings captured.

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

Installed in 3 minutes.
Recovered from all 7 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed Apache-2.0, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

An agent with no time limit did not get it running.

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 by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Unverified	80.00	0.07	2026-09-26 22:36 UTC
Argusic Runner	1/3	Unverified	80.00	0.03	2026-09-26 22:22 UTC

Topics (from GitHub)

aiagent app-builder crud-application developer-tool developer-tools gui hacktoberfest internal-development internal-tool internal-tools low-code low-code-development-platform lowcode react self-hosted typescript

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/illa-builder.svg)](https://argusic.com/subject/illa-builder)

Questions

Does illa-builder run?: Argusic could not verify that illa-builder runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test illa-builder?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit a468660903e2. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test illa-builder?: The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does illa-builder take to install?: 3 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 illa-builder need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing illa-builder?: 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for illa-builder?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.