fluidity
Fluidity - An accordion based startpage
Runssource: GitHubhomepageTypeScriptMITcommit f502de59f4a6
TypeScript, MIT licensed. The project labels itself: emotionjs, github page, react, startpage and typescript.
fluidity runs. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install completes cleanly (except node engine warnings for 2 packages), vite build produces a working dist/ directory, and both npm run start (dev server) and npm run serve (preview) boot successfully, serving the startpage at localhost.
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 90 of 100 (the mean of this project's run scores).
At a glance
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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- @pretty-cozy/[email protected] failed to install — its transitive dep @pretty-cozy/eslint-plugin does not exist in npm registry
- [email protected] requires Node >=20.19 but container has Node 18.19.1
- Install time
- 1 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- Model tokens used
- 32,192
- Exact commit tested
- f502de59f4a6
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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.
2. **`[email protected]` requires Node >=20.19, but we have Node 18.19.1** — downgraded to `[email protected]` a… 3. **Node engine warnings for `@fortawesome/[email protected]`** (requires >=20) — these are … **No third-party keys were needed** since this is a static frontend startpage app. Everything runs … tokens used 32,192 Everything works. Now let me compile the results. Here's the summary: **Errors encountered:** 1. **`@pretty-cozy/[email protected]` had an unresolvable dependency `@pretty-cozy/eslint… 2. **`[email protected]` requires Node >=20.19, but we have Node 18.19.1** — downgraded to `[email protected]` a… 3. **Node engine warnings for `@fortawesome/[email protected]`** (requires >=20) — these are … **No third-party keys were needed** since this is a static frontend startpage app. Everything runs …
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.
- Installed in 1 minute.
- Recovered from all 2 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1 minutes after the clone.
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 | 1/3 | Runs | 100.00 | 0.03 | |
| Argusic Runner | 2/3 | Unverified | 80.00 | 0.04 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/fluidity)Questions
- Does fluidity run?
- Yes. fluidity runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test fluidity?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f502de59f4a6. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test fluidity?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does fluidity take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does fluidity need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing fluidity?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for fluidity?
- 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.