mantrae

Web UI for managing Traefik

Runssource: GitHubhomepageTypeScriptMITcommit 10e1ee319e7e

TypeScript, MIT licensed. The project labels itself: go, reverse proxy, svelte, traefik and ui.

mantrae runs. An Argusic agent installed it in 3 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Go binary builds and runs, SvelteKit frontend builds and is embedded, server launches on port 3000 and serves the web UI with HTTP 200 on all static routes.

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.07 (measured)
recorded runs
1
last tested
stars
493
forks
27
open issues
8
watchers
3
size
9 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 mantrae, 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.

  • Go compiler not pre-installed1 minute
  • Node.js v18 too old for rolldown (needs node:util.styleText from Node 22+)1 minute
  • Initial pnpm install under Node 18 downloaded wrong native bindings for rolldown0.5 minutes
Install time
3 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
curl -s http://localhost:3000/ returned HTTP 200 with 5856 bytes of SvelteKit HTML; curl -s http://localhost:3000/openapi.json returned HTTP 200 with 240594 bytes; curl -s http://localhost:3000/favicon.ico returned HTTP 200; go test ./... exited 0; server --version printed 'mantrae version dev (commit: test, built: now)'
Model tokens used
236,893
Exact commit tested
10e1ee319e7e
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.

- **Node.js**: v18 was pre-installed but couldn't build (rolldown needs `node:util.styleText` from …
- **pnpm**: Installed globally via npm (Node 22) to `/home/runner/.local/bin`
- **Frontend**: `pnpm install` + `pnpm build` completed successfully — static site output in `web/u…
- **Go binary**: `go build` produced `/tmp/mantrae` (172 MB, CGO_ENABLED=0); `--version` prints cor…
- **Server launch**: Started with `SECRET=$(openssl rand -hex 16)`; responds 200 with the Svelte SP…
- **Tests**: `go test ./...` exits 0 (all 22 packages have no test files)
**End-to-end verification results:**
- `GET /` → HTTP 200, 5856 bytes (SvelteKit HTML with `<html lang="en">` head)
- `GET /healthz` → 200
- `GET /openapi.json` → 200, 240 KB
- `GET /favicon.ico` → 200, 15 KB
- `GET /mantrae.v1.UserService/` → 404 (expected; ConnectRPC requires POST + protobuf)

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.

What did not, or is not known

  • Took 3 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 12 go projects Argusic has installed and timed, mantrae was the 9th fastest to reach a running state, and 12 of 12 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 3 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

goreverse-proxysveltetraefikui

Embed the badge

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

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

Questions

Does mantrae run?
Yes. mantrae runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test mantrae?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 10e1ee319e7e. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test mantrae?
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 mantrae take to install?
3 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 mantrae need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing mantrae?
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 mantrae compare with the alternatives?
Of the 12 go projects Argusic has installed and timed, mantrae was the 9th fastest to reach a running state, and 12 of 12 reached one at all.
Where is the evidence for mantrae?
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