lunarr-go
Self-hosted media streaming server designed as an alternative to Plex, allowing you to monitor and manage your movie and TV show files on a headless server.
Runssource: GitHubhomepageTypeScriptApache-2.0commit af35226b6a86
TypeScript, Apache-2.0 licensed. The project labels itself: emby, jellyfin, kodi, lunarr, media organizer, media server, nodejs and plex.
lunarr-go runs. An Argusic agent installed it in 6 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Project builds from source, all 1136 automated tests pass, production server starts and serves the setup/admin registration page on port 3000, and all FFmpeg/NodeAV playback runtime verifications 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 100 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.
- Bun not installed in container1 minute
- Node.js 18 lacks styleText export from node:util needed by rolldown1 minute
- bun not on PATH for npm test script
- Install time
- 6 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm run build exited 0; bun test exited 0 with 1136 pass; node scripts/start.mjs launched and curl returned HTTP 303 on / and served /setup HTML; node scripts/verify-ffmpeg.mjs, verify-nodeav-probe.mjs, smoke-ffmpeg-transcode.mjs, verify-runtime.mjs all exited 0
- Model tokens used
- 51,451
- Exact commit tested
- af35226b6a86
- 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.
1. **Bun not installed** — The project requires Bun but only Node.js was available. Fixed by downlo… 2. **Node.js 18 too old for rolldown** — `svelte-kit sync` and `vite build` need `styleText` from `… 3. **bun test PATH issue** — `npm test` invokes `bun test` but Bun wasn't on PATH. Worked around by… **Verification performed:** - `npm run build` via Node 22 built successfully (SSR + client, 7.21s) - `bun test` exited with 1136 pass, 0 fail across 138 files - `node scripts/start.mjs` launched the production server on port 3000, responding with HTTP 303 → … - `verify:ffmpeg` — passed - `verify:nodeav` — passed (mov,mp4,m4a, 1 video stream, 3.000s) - `smoke:transcode` — both HLS transcode and copied-remux smokes passed - `verify:runtime` — passed (FFmpeg + NodeAV + transcode) No external credentials were mocked because nothing external was needed to verify the app.
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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 6 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 emby projects Argusic has installed and timed, lunarr-go was the 4th fastest to reach a running state, and 3 of 4 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 6 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
Topics (from GitHub)
embyjellyfinkodilunarrmedia-organizermedia-servernodejsplexself-hostedtv-seriestv-showstypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lunarr-go)Questions
- Does lunarr-go run?
- Yes. lunarr-go runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test lunarr-go?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit af35226b6a86. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test lunarr-go?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does lunarr-go take to install?
- 6 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 lunarr-go need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lunarr-go?
- 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 lunarr-go compare with the alternatives?
- Of the 4 emby projects Argusic has installed and timed, lunarr-go was the 4th fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for lunarr-go?
- 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.