Amagine3D
Amagine3D: From hardware requirements to editable 3D designs
Runssource: GitHubPythonApache-2.0commit fa63d138f453
Python, Apache-2.0 licensed.
Amagine3D runs. An Argusic agent installed it in 3.9 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Node.js v22.19.0 installed from tarball, npm packages installed, Python 3.12 venv with build123d/lib3mf/manifold3d/trimesh created, TypeScript typechecks clean, Vite build produces dist/, all 128 tests pass, server starts on :6161 and responds to tRPC queries, a3d CLI prints help
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.
- Install time
- 4 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm test exited 0, 128 passed 1 skipped 0 failed; curl to tRPC health endpoint returned 200 with valid API contract
- Model tokens used
- 38,104
- Exact commit tested
- fa63d138f453
- 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.
2026-09-29T10:21:58.679763Z ERROR codex_core::session: failed to record rollout items: thread 01a0e… tokens used 38,104 Amagine3D is fully operational. Key steps and results: - **Node.js upgrade**: v18.19.1 → v22.19.0 (downloaded tarball, extracted to `/tmp/node-v22.19.0-li… - **npm install**: 353 packages, no errors - **Python setup** (`.venv`): Python 3.12.3 venv created with `build123d`, `lib3mf`, `manifold3d`, … - **`npm test`**: 128 passed, 1 skipped, 0 failed - **`npm run typecheck`**: zero diagnostics - **`npm run build`**: Vite build complete, output in `dist/` - **Server**: starts on `127.0.0.1:6161` and serves the workbench HTML + tRPC endpoint; health quer… - **`a3d` CLI**: help output shows all 17+ subcommands
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 3.9 minutes, faster than the median of the 19 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, 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.
Of the 20 Python projects Argusic has installed and timed, Amagine3D was the 7th fastest to reach a running state, and 11 of 20 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.9 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/amagine3d)Questions
- Does Amagine3D run?
- Yes. Amagine3D runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test Amagine3D?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit fa63d138f453. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Amagine3D?
- 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 Amagine3D take to install?
- 3.9 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 Amagine3D need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Amagine3D?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does Amagine3D compare with the alternatives?
- Of the 20 Python projects Argusic has installed and timed, Amagine3D was the 7th fastest to reach a running state, and 11 of 20 reached one at all.
- Where is the evidence for Amagine3D?
- 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.