ShadowEditor
Cross-platform 3D scene editor based on three.js, golang and mongodb for desktop and web.
Runssource: GitHubhomepageJavaScriptMITcommit 49a6e7d506d3
JavaScript, MIT licensed. The project labels itself: editor, game engine, gis, golang, lol, scene, shadow editor and three.
ShadowEditor runs. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ShadowEditor v0.6.1 server running on port 2020 serving the web frontend and all API endpoints (Config/Get, Assets/List, Category/List, Mesh/List, Scene/List, Material/List) return Code:200. MongoDB stores data without auth. Static files (HTML, JS, CSS, favicon) served correctly.
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.
- MongoDB not installed. Required for the Go server backend. Downloaded mongodb-linux-x86_64-ubuntu2204-7.0.0.tgz2 minutes
- Go language not installed in environment. Downloaded go1.21.0 tarball from golang.org1 minute
- npm dependencies had deprecation warnings but installed successfully
- Install time
- 8 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- curl http://localhost:2020/ returned HTTP 200; curl http://localhost:2020/api/Config/Get returned {"Code":200}; curl http://localhost:2020/api/Assets/List returned {"Code":200}; all 11 tested endpoints (/, index.html, favicon.ico, ShadowEditor.js, ShadowEditor.css, /api/Config/Get, /api/Assets/List, /api/Category/List, /api/Mesh/List, /api/Scene/List, /api/Material/List) returned HTTP 200
- Model tokens used
- 77,107
- Exact commit tested
- 49a6e7d506d3
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
GET /api/Material/List : 200 GET /build/ShadowEditor.js : 200 GET /build/ShadowEditor.css : 200 GET /favicon.ico : 200 GET /index.html : 200 All endpoints return 200. Let me now compile the final report. The total time was about 8 minutes (started ~19:17, now ~19:25). 2026-11-13T19:24:20.815951Z ERROR codex_core::session: failed to record rollout items: thread 01a1d… tokens used 77,107 All endpoints return 200. Let me now compile the final report. The total time was about 8 minutes (started ~19:17, now ~19:25).
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 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
Of the 8 editor projects Argusic has installed and timed, ShadowEditor was the 5th fastest to reach a running state, and 7 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 8 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
Topics (from GitHub)
editorgame-enginegisgolanglolsceneshadow-editorthreethree-editorthreejsweb-giswebgl
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/shadoweditor)Questions
- Does ShadowEditor run?
- Yes. ShadowEditor runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test ShadowEditor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 49a6e7d506d3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ShadowEditor?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ShadowEditor take to install?
- 8 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 ShadowEditor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ShadowEditor?
- 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.
- How does ShadowEditor compare with the alternatives?
- Of the 8 editor projects Argusic has installed and timed, ShadowEditor was the 5th fastest to reach a running state, and 7 of 8 reached one at all.
- Where is the evidence for ShadowEditor?
- 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.