thing-editor
pixi.js based visual game editor
Runssource: GitHubTypeScriptMITcommit 695d0bd8246f
TypeScript, MIT licensed. The project labels itself: 2d game, editor, game, game engine, gamedev, games, html5 game development and javascript.
thing-editor runs. An Argusic agent installed it in 30 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
With npm i done and vite running, the Electron editor opens on the Xvfb display, loads the editor UI, and its headless mode builds the example project (release and debug bundles with decodable media and resolvable assets) then exits printing 'build finished'.
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 90 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.
- Electron SUID chrome-sandbox not configured (requires root) - app aborted with SIGTRAP2 minutes
- Electron renderer got ERR_CONNECTION_REFUSED on http://localhost:5173/ because the vite dev server died with the invoking shell1 minute
- npm run build (tsc && vite build) fails on editor auto-generated typings (prefabs-typing.ts, ThingSceneAllMap, GameClasses) that only exist at runtime
- Install time
- 30 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- DISPLAY=:99 IS_CI_RUN=true npx electron ./thing-editor/electron-main --no-sandbox --build-and-exit=example-project --no-vscode-integration printed 'FS-LOG: build release', 'FS-LOG: build debug', 'BUILD COMPLETE: http://localhost:5174/games/example-project/', 'build finished' and exited, repeated 3x; probe run of games/example-project/release/index.html in Electron returned PAGE-STATE {"title":"","canvases":1,...} with EXIT=0; ffmpeg -v error -i <aac/ogg> -f null - returned exit 0
- Model tokens used
- 273,099
- Exact commit tested
- 695d0bd8246f
- 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.
(DISPLAY=:99 IS_CI_RUN=true npx electron ./thing-editor/electron-main --no-sandbox --build-and-exit… sleep 35 tail -2 /tmp/electron.log # 5) built game behaves: run release bundle in Electron, expect PAGE-STATE canvases:1 DISPLAY=:99 IS_CI_RUN=true npx electron --no-sandbox --disable-gpu /tmp/probe.js http://localhost:5… EOF chmod +x /tmp/thing-editor-verification.sh && echo saved && ls -la /tmp/probe.js" in /work/repo succeeded in 0ms: saved -rw-rw-r-- 1 runner runner 1208 Oct 21 20:00 /tmp/probe.js tokens used 273,099
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 30 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.
- Measured 2 times, so the result is not a one-off.
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 by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.07 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.02 |
Topics (from GitHub)
2d-gameeditorgamegame-enginegamedevgameshtml5-game-developmentjavascriptpixi-jspixijstypescriptunity-analoguewebgl
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/thing-editor)Questions
- Does thing-editor run?
- Yes. thing-editor runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test thing-editor?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 695d0bd8246f. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test thing-editor?
- 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 thing-editor take to install?
- 30 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 thing-editor need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing thing-editor?
- 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 thing-editor?
- 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.