tasking-manager

Tasking Manager - The tool to team up for mapping in OpenStreetMap

Runs with mockssource: GitHubhomepagePythonBSD-2-Clausecommit 2b917a14ea7b

Python, BSD-2-Clause licensed. The project labels itself: fastapi, javascript, openstreetmap, postgis, postgresql, python and reactjs.

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

FastAPI backend (Python 3.10, uv-managed) starts successfully on port 5000 against an embedded PostgreSQL 18.6 database, serving the Tasking Manager API with 149 endpoints and Swagger UI documentation.

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.12 (measured)
recorded runs
1
last tested
stars
613
forks
328
open issues
472
watchers
31
size
68 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 tasking-manager, 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.

  • Test suite uses Flask patterns (BaseTestCase imports create_app, Flask, flask_sqlalchemy) but the backend has been migrated to FastAPI. Tests fail to import because create_app and Flask SQLAlchemy session are no longer defined in the backend module.60 minutes
  • PostgreSQL not available on system (no apt, no root). Required for both runtime and tests.20 minutes
  • Frontend npm install hangs indefinitely — likely network connectivity issue or large dependency graph timing out.10 minutes
Install time
60 minutes
Cold machine to finish
26 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
uvicorn backend.main:api started on 0.0.0.0:5000 with embedded PostgreSQL. curl -L http://localhost:5000/ returned 200 (redirect to docs). curl http://localhost:5000/api/docs returned 200 (Swagger UI HTML). curl http://localhost:5000/api/openapi.json returned 200 with 'Tasking Manager' title and 149 API paths.
Model tokens used
565,877
Exact commit tested
2b917a14ea7b
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.

  /api/v2/badges/{badge_id}/
  /api/v2/campaigns/
 ...
  /api/v2/users/{username}/recommended-projects/
  /api/v2/users/{username}/statistics/
  /api/v2/users/{username}/statistics/
  /docs/oauth2-redirect
  /redoc
Final summary — I've verified the complete state of the repository. Here's what I found:
tokens used
565,877
Final summary — I've verified the complete state of the repository. Here's what I found:

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 60 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed BSD-2-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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.12

Topics (from GitHub)

fastapijavascriptopenstreetmappostgispostgresqlpythonreactjs

Embed the badge

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

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

Questions

Does tasking-manager run?
tasking-manager runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 60 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test tasking-manager?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2b917a14ea7b. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test tasking-manager?
The run that produced this verdict cost $0.12: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does tasking-manager take to install?
60 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 tasking-manager need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing tasking-manager?
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 tasking-manager?
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.

Discussion