tilemill runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 1 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test tilemill?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit d2c8348aa8d0. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test tilemill?

The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does tilemill take to install?

1.2 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 tilemill need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing tilemill?

5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for tilemill?

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.

tilemill

TileMill is a modern map design studio

Runs with mockssource: GitHub homepageJavaScriptBSD-3-Clausecommit d2c8348aa8d0

JavaScript, BSD-3-Clause licensed. The project labels itself: mapbox, mapnik, openstreetmap, osm and tilemill.

tilemill runs, with stand-ins for the services it depends on. An Argusic agent installed it in 1.2 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Server starts on ports 20008/20009, responds HTTP 200 on all endpoints, 24 of 30 mocha tests pass including config CRUD, project CRUD, abilities, export create/delete, and duplicate module detection for sqlite3/mapnik.
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 92 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 92 / 100
cost of the verifying run: $0.24 (measured)
recorded runs: 1
last tested: 2026-10-01
stars: 3,150
forks: 517
open issues: 407
watchers: 151
size: 120 MB
created: 2010-07-05
last push: 2026-09-06

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-01. 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 tilemill, 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.

npm install failed on native modules (mapnik, gdal, sqlite3, zipfile) - node-pre-gyp cannot download pre-built binaries (HTTP 403 from S3) and source compilation fails against system Mapnik 3.1 (node-mapnik 3.7.2 expects Mapnik 3.0.20 headers, also ICU and mapbox/variant headers mismatch)18 minutes
node 18.19.1 not supported - TileMill requires node 8.x5 minutes
PostgreSQL/PostGIS not available - 3 datasource tests fail
Tile rendering tests fail - mock mapnik cannot produce real PNG tiles
Export anti-meridian test fails - S3 download URL returns 403

Install time: 1 minutes
Cold machine to finish: 39 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
How the result was proved: curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:20909/ returned 200, /api/Config/config returned 200 with valid JSON, /status returned 200, /assets/tilemill/js/abilities.js returned valid JS. `npx mocha --timeout 100000` exits with 24 passing, 6 failing.
Model tokens used: 225,874
Exact commit tested: d2c8348aa8d0
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
Behaviour against real services: this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

=== Test summary ===
15 config/project/abilities tests: all pass
2 duplicate_module tests (sqlite3, mapnik): pass
7 export tests: 6 pass, 1 fail (S3 download)
6 tile tests: 3 pass, 3 timeout/fail (no real mapnik rendering)
3 datasource tests: all fail (no postgres)
=== Server verified ===
HTTP/1.1 200 OK on /, /api/Config/config, /status, /assets/tilemill/js/abilities.js
2026-10-01T16:57:33.563312Z ERROR codex_core::session: failed to record rollout items: thread 01a0f…
2026-10-01T16:57:33.563350Z ERROR codex_core::session: failed to record rollout items: thread 01a0f…
tokens used
225,874

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

Installed in 1.2 minutes.
Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed BSD-3-Clause, as reported by its host.

What did not, or is not known

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

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	1/3	Runs with mocks	92.00	0.24	2026-10-01 16:57 UTC

Topics (from GitHub)

mapbox mapnik openstreetmap osm tilemill

Embed the badge

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

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

Questions

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