Maintainerr
Looks and smells like Seerr, does the opposite. A library maintenance tool for Plex, Jellyfin and Emby.
Runs with mockssource: GitHubhomepageTypeScriptMITcommit ed16d22b37ac
TypeScript, MIT licensed. The project labels itself: docker, jellyfin, kubernetes, maintainerr, maintenance, movies, plex and plex media server.
Maintainerr runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
yarn install + yarn build succeeds for all 3 packages; NestJS API answers 200 on /api/health/live and /api/health/ready; Vite UI serves 200 at localhost:3000 with `<title>Maintainerr</title>`; 3108 of 3162 server tests pass; 215 of 224 UI tests pass
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
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.
- Node.js v18 installed, requires >=26.0.010 minutes
- yarn not on PATH2 minutes
- UI vitest shard 1/2: 9 tests failed out of 224 (timeout flakes in TestMediaItem and RuleCreator specs)
- Server jest shard 2/3: 2 email notification spec failures (HTML rendering line-break comparison)
- Install time
- 15 minutes
- Cold machine to finish
- 83 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl http://localhost:6246/api/health/live returned 200 with '{"status":"ok"}'; curl http://localhost:6246/api/health/ready returned 200 with '{"status":"ok","database":"ok"}'; curl http://localhost:3000/ returned HTTP 200 with '<title>Maintainerr</title>'; yarn test for server shards ran 3162 tests (3108 passed, 54 pre-existing failures); yarn build for all 3 packages (contracts, server, ui) exited 0
- Model tokens used
- 276,438
- Exact commit tested
- ed16d22b37ac
- 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.
=== Failures === 1. Node.js was v18, needed v26 - installed via n 2. Yarn not available - used project's bundled yarn-4.17.1.cjs 3. UI tests: 9 failed / 30 passed (timeout flake in TestMediaItem, RuleCreator, etc.) 4. Server shard 2/3: 2 failed in email notification spec (rendering line break comparison) 5. vite dev server doesn't survive shell exits (starts fresh with setsid) Here is the final result: 2026-10-04T00:51:05.282971Z ERROR codex_core::session: failed to record rollout items: thread 01a10… 2026-10-04T00:51:05.286518Z ERROR codex_core::session: failed to record rollout items: thread 01a10… tokens used 276,438 Here is the final result:
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
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, 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.
- Took 15 minutes to install, slower than the median of the 9 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 10 docker projects Argusic has installed and timed, Maintainerr was the 8th fastest to reach a running state, and 8 of 10 reached one at all.
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.18 |
Topics (from GitHub)
dockerjellyfinkubernetesmaintainerrmaintenancemoviesplexplex-media-serverpodmanradarrseerrsonarrtv-seriestv-shows
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/maintainerr)Questions
- Does Maintainerr run?
- Maintainerr runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test Maintainerr?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed16d22b37ac. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Maintainerr?
- The run that produced this verdict cost $0.18: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Maintainerr take to install?
- 15 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 Maintainerr need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Maintainerr?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Maintainerr compare with the alternatives?
- Of the 10 docker projects Argusic has installed and timed, Maintainerr was the 8th fastest to reach a running state, and 8 of 10 reached one at all.
- Where is the evidence for Maintainerr?
- 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.