BubbleLab

Open-core workflow engine powering Bubble Lab, and fully runnable, hostable, and extensible on its own.

Runssource: GitHubhomepageTypeScriptApache-2.0commit e64b2469659b

TypeScript, Apache-2.0 licensed. The project labels itself: ai, ai agents, apis, cli, code, developer tool, development and integrations.

BubbleLab runs. An Argusic agent installed it in 45 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

BubbleLab installs, builds, and launches with pnpm install && pnpm build:core && pnpm run dev (setup-env creates .env files, builds core packages, starts bubblelab-api on :3001 and bubble-studio on :3002). All 182 tests pass with --concurrency=1; 1 AI-model integration test fails due to generated code not passing validation.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.29 (measured)
recorded runs
2
last tested
stars
1,099
forks
183
open issues
41
watchers
5
size
40 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 BubbleLab, 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 is too old, project requires >=202 minutes
  • bun not found (required by bubblelab-api)2 minutes
  • pnpm not found in PATH1 minute
  • SQLITE_BUSY errors when running full test suite due to concurrent test files
  • boba.test.ts AI generation test fails with real OPENROUTER_API_KEY - generated code doesn't pass TypeScript validation
Install time
45 minutes
Cold machine to finish
46 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
pnpm build:core succeeded, pnpm build succeeded (6 tasks). Server launched on port 3001 (GET /bubble-flow returned 200). Bubble Studio launched on port 3002 (GET / returned 200). Test suite: 182 passed, 21 skipped, 1 fail (boba AI test).
Model tokens used
405,653
Exact commit tested
e64b2469659b
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

The end of the recording

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

- bubblelab-api: **182 pass, 21 skip, 1 fail** (the 1 failure is `boba.test.ts` "should generate a …
- bubble-runtime: **175 pass, 1 skip** (all passed)
- Other packages had no test scripts defined.
**Errors encountered and fixes:**
1. **Node.js version too old (v18)** - Project requires >=20. Fixed by installing nvm and using `nv…
2. **pnpm not installed** - Installed via `npm install -g pnpm --prefix /home/runner/.local`.
3. **bun not installed** - The API server requires bun. Downloaded bun binary ZIP from GitHub and e…
4. **SQLITE_BUSY errors in tests** - Tests share a single `test.db` and bun test runs test files co…
5. **AI model test failure** - `boba.test.ts` runs because `OPENROUTER_API_KEY` is set in the envir…
**Launch verification:**
- bubblelab-api started on port 3001: `GET /bubble-flow` → `200 OK`
- bubble-studio started on port 3002: `GET /` → `200 OK`

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

  • Reached a running state on a clean machine, with the session recorded.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • 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

  • Took 45 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.

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

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 Runner2/3Runs100.000.29
Argusic Runner1/3Runs100.000.11

Topics (from GitHub)

aiai-agentsapisclicodedeveloper-tooldevelopmentintegrationsopen-sourceworkflowworkflow-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/BubbleLab.svg)](https://argusic.com/subject/bubblelab)

Questions

Does BubbleLab run?
Yes. BubbleLab runs. Argusic installed and launched it on a clean machine in 45 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test BubbleLab?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e64b2469659b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test BubbleLab?
The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does BubbleLab take to install?
45 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 BubbleLab need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing BubbleLab?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does BubbleLab compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, BubbleLab was the 232nd fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for BubbleLab?
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.

Discussion