Amagine3D

Amagine3D: From hardware requirements to editable 3D designs

Runssource: GitHubPythonApache-2.0commit fa63d138f453

Python, Apache-2.0 licensed. The project labels itself: 3d printing tools, text to 3d and text to cad.

Amagine3D runs. An Argusic agent installed it in 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.

Install, typecheck, test suite, and build all succeeded; web and API answered 200; a3d compile produced decoded STEP/STL/3MF/GLB/PNG artifacts for simple-brep measuring 40x28x10 mm in /work/repo/workspace/e2e-1.

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
6,289
forks
536
open issues
4
watchers
56
size
7 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 Amagine3D, 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.

  • a3d compile failed with CONTRACT.INTENT_MUTATED and invalid intent when the intent JSON path was passed as the scene argument5 minutes
  • System Node v18.19.1 below required >=22.19.0; npm ci refused the engine2 minutes
Install time
5 minutes
Cold machine to finish
51 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
npm test exited 0 (128 passed, 1 skipped); npm run test:python exited 0 (441 OK); curl on :6160 and :6161 returned 200; a3d compile exited 0 with pass:true and artifacts decoded via trimesh/build123d/PIL
Model tokens used
571,035
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.

- Ran the real CAD pipeline in `workspace/e2e-1/`: `a3d profile` (bbl-a1-mini-0.4 profile), intent …
- Decoded artifacts (not just headers): STL watertight, 9956 faces, 40×28×10 mm, volume 10264.2 mm³…
Useful files: `/work/repo/workspace/e2e-1/simple-brep.step`, `simple-brep.stl`, `simple-brep.3mf`, …
tokens used
571,035
All verified. Here's the report.
**What I did**
- Read `README.md` and `AGENTS.md`, then installed as a fresh user: `npm ci` (exit 0), `.env` from …
- Launched `npm run dev`: web `http://127.0.0.1:6160` → 200; API tRPC health on `:6161` → 200 with …
- Ran the real CAD pipeline in `workspace/e2e-1/`: `a3d profile` (bbl-a1-mini-0.4 profile), intent …
- Decoded artifacts (not just headers): STL watertight, 9956 faces, 40×28×10 mm, volume 10264.2 mm³…
Useful files: `/work/repo/workspace/e2e-1/simple-brep.step`, `simple-brep.stl`, `simple-brep.3mf`, …

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 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 5 minutes to install, slower than the median of the 46 comparable projects Argusic has measured.

Of the 47 Python projects Argusic has installed and timed, Amagine3D was the 34th fastest to reach a running state, and 32 of 47 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 5 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.29
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

3d-printing-toolstext-to-3dtext-to-cad

Embed the badge

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

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

Questions

Does Amagine3D run?
Yes. Amagine3D runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 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. 2 attempts are 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.29: 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?
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 Amagine3D need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Amagine3D?
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 Amagine3D compare with the alternatives?
Of the 47 Python projects Argusic has installed and timed, Amagine3D was the 34th fastest to reach a running state, and 32 of 47 reached one at all.
Where is the evidence for Amagine3D?
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