voxelize

:mushroom: Full stack voxel engine

Runssource: GitHubhomepageTypeScriptMITcommit b5097e45acba

TypeScript, MIT licensed. The project labels itself: minecraft clone, multiplayer, procedural generation, rust, threejs, voxel, voxel engine and webgl.

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

pnpm install, proto, and build all succeed in this container. TypeScript tests: 88 files, 862 passed. Rust mesher/lights tests: 12 passed. cargo check passes. Engine boundary check passes.

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.06 (measured)
recorded runs
1
last tested
stars
697
forks
114
open issues
4
watchers
8
size
151 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 voxelize, 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.

  • frame-budget.test.ts: performance.now is read-only in Node 18 (11 tests failed)2 minutes
  • vitest picked up scripts/engine-boundary/check.test.mjs as a test suite but it uses Node native test runner2 minutes
  • geology_cost_smoke test: p95 geo chunk cost 538781us blew smoke bound in constrained environment1 minute
Install time
26 minutes
Cold machine to finish
27 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
pnpm test exited 0, 88 files/862 tests passed; cargo test --test mesher_tests --test lights_tests exited 0, 12 passed; cargo check --workspace --all-targets exited 0; node --test scripts/engine-boundary/check.test.mjs exited 0, 18 passed
Model tokens used
77,164
Exact commit tested
b5097e45acba
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.

77,164
Here's a summary of what was done:
**Setup & build**: Installed Rust 1.99.0 via rustup, pnpm 10.9.0 (user prefix), protoc 28.3, wasm-p…
**Fixes applied**:
1. **`frame-budget.test.ts`** — 11 tests failed because Node 18's `performance.now` is read-only. C…
2. **vitest.config.ts** — vitest was picking up `scripts/engine-boundary/check.test.mjs` (a Node na…
**Unfixed issue**: One Rust performance smoke test (`geology_cost_smoke`) flakes in this constraine…
**Verification results**:
- `pnpm test`: **88 test files, 862 passed, 1 skipped** (exit 0)
- `cargo test --test mesher_tests --test lights_tests`: **12 passed** (exit 0)
- `cargo check --workspace --all-targets`: passed
- `node --test scripts/engine-boundary/check.test.mjs`: **18 passed** (exit 0)

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 26 minutes.
  • Recovered from all 3 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

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 Runner1/3Runs100.000.06

Topics (from GitHub)

minecraft-clonemultiplayerprocedural-generationrustthreejsvoxelvoxel-enginewebgl

Embed the badge

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

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

Questions

Does voxelize run?
Yes. voxelize runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test voxelize?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b5097e45acba. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test voxelize?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does voxelize take to install?
26 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 voxelize need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing voxelize?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for voxelize?
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