lavish-axi
HTML is the new markdown. Lavish is the new editor for your HTML artifacts.
Runssource: GitHubJavaScriptMITcommit 5f0be78ff9ef
JavaScript, MIT licensed.
lavish-axi runs. An Argusic agent installed it in 3.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm install resolved 390 packages, build produced dist/cli.mjs (625 KB), all pre-submit checks pass (lint, typecheck, format, skill/plugin freshness), 1391/1415 tests pass with 0 failures, and the CLI launches a real artifact session on 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 100 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.
- pnpm not found in PATH0.5 minutes
- Node v18.19.1 < required v22 (engine warning)
- Install time
- 4 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- node --test exited 0, 1391 passed 0 failed 24 skipped; node dist/cli.mjs --version returned 0.1.80; lavish-axi /tmp/test-artifact.html --port 0 started server and returned session URL with status 'opened'
- Model tokens used
- 30,931
- Exact commit tested
- 5f0be78ff9ef
- 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.
session: file: /tmp/test-artifact.html url: "http://127.0.0.1:4387/session/6e61b56b5b8cdb8b" status: opened self_paint_warning: "This artifact never paints its own page surface: no background on html/body/:r… next_step: "First fix the unpainted page surface flagged in self_paint_warning and save - Lavish li… The application works end-to-end. Let me make sure I clean up the temp state and record the final v… 2026-10-03T07:20:16.003272Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… Here's my final report. tokens used 30,931 Here's my final report.
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 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.
What did not, or is not known
- Took 3.5 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 8 JavaScript projects Argusic has installed and timed, lavish-axi was the 6th fastest to reach a running state, and 5 of 8 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.
- A quick evaluation: it was running 3.5 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lavish-axi)Questions
- Does lavish-axi run?
- Yes. lavish-axi runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test lavish-axi?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5f0be78ff9ef. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test lavish-axi?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does lavish-axi take to install?
- 3.5 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 lavish-axi need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lavish-axi?
- 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.
- How does lavish-axi compare with the alternatives?
- Of the 8 JavaScript projects Argusic has installed and timed, lavish-axi was the 6th fastest to reach a running state, and 5 of 8 reached one at all.
- Where is the evidence for lavish-axi?
- 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.