SuggestArr

Effortlessly request recommended movies, TV shows and anime to Jellyseer/Overseer based on your recently watched content on Jellyfin, Plex or Emby, let SuggestArr handle it all automatically, keeping your library fresh with new and exciting content!

Runssource: GitHubhomepagePythonMITcommit 809353da4dc1

Python, MIT licensed. The project labels itself: automation, docker, emby, jellyfin, jellyseerr, llm, media automation and ombi.

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

Python backend installs and runs: 1050/1050 tests pass, Flask app starts on port 5000 with all 25 database tables created, Swagger UI serves at /docs, health endpoint returns 200, and public API v1 status endpoint returns 200.

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.03 (measured)
recorded runs
2
last tested
stars
1,395
forks
45
open issues
2
watchers
3
size
17 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 SuggestArr, 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.

  • PEP 668 externally-managed environment blocks system-wide pip install1 minute
Install time
14 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
pytest: 1050 passed in 29.57s; curl http://localhost:5000/api/v1/status returned 200 with {"data":{"api_version":"v1","service":"SuggestArr","status":"ok"}}; curl http://localhost:5000/api/health/live returned 200 with {"status":"ok"}
Model tokens used
148,911
Exact commit tested
809353da4dc1
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.

      "msg": "PEP 668 externally-managed environment blocks system-wide pip install",
      "fix": "Created Python virtual environment at /work/repo/.venv",
      "minutes": 1
    }
  ],
  "test_depth": "tier1_real",
  "verified_how": "pytest: 1050 passed in 29.57s; curl http://localhost:5000/api/v1/status returned…
  "notes": "Node.js 18 is too old (Vite 6 requires 20.19+) so the Vue frontend cannot be built in t…
  "final_state": "Python backend installs and runs: 1050/1050 tests pass, Flask app starts on port …
}
tokens used
148,911

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 1 error 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 did not, or is not known

  • Took 14 minutes to install, slower than the median of the 38 comparable projects Argusic has measured.

Of the 39 automation projects Argusic has installed and timed, SuggestArr was the 37th fastest to reach a running state, and 27 of 39 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.

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 Runner2/3Runs100.000.03
Argusic Runner1/3Runs100.000.01

Topics (from GitHub)

automationdockerembyjellyfinjellyseerrllmmedia-automationombiopen-sourceopenaioverseerrplexself-hostedtmdbtrakt

Embed the badge

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

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

Questions

Does SuggestArr run?
Yes. SuggestArr runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test SuggestArr?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 809353da4dc1. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test SuggestArr?
The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does SuggestArr take to install?
14 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 SuggestArr need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing SuggestArr?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does SuggestArr compare with the alternatives?
Of the 39 automation projects Argusic has installed and timed, SuggestArr was the 37th fastest to reach a running state, and 27 of 39 reached one at all.
Where is the evidence for SuggestArr?
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.

Discussion