jellyfin-webos
WebOS Client for Jellyfin
Runs with mockssource: GitHubhomepageJavaScriptMPL-2.0commit ab4794046467
JavaScript, MPL-2.0 licensed. The project labels itself: jellyfin, jellyfin client and webos.
jellyfin-webos runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
npm install completes, ares-package builds a valid IPK with no errors, ares-package --check reports no problems, all frontend JavaScript executes correctly in dependency order, and the backend discovery service starts and handles subscriptions, requests, and cancellations correctly with a mocked webos-service SDK.
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 86 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.
- Install time
- 3 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- npm install succeeded (543 packages); ares-package --check returned 'no problems detected'; all frontend JS executed in dependency order in mock browser context; backend service loaded with mocked webos-service, UDP listener bound on port 7359, subscription/request/cancel handlers registered and invoked; ares-server served all 9 frontend files at HTTP 200; IPK verified via ares-package -I showing correct app+service structure
- Model tokens used
- 171,463
- Exact commit tested
- ab4794046467
- 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.
19:21:42 Here's the final assessment. **Install:** npm install succeeded (543 packages), ares-package built the IPK without error, ares-p… **Errors:** none. The `webos-service` npm module is proprietary (LG SDK) and unavailable on public … **Verification:** frontend JS executed end-to-end in mock browser context (all 6 files in dependenc… 2026-10-12T19:21:52.719457Z ERROR codex_core::session: failed to record rollout items: thread 01a13… tokens used 171,463 Here's the final assessment. **Install:** npm install succeeded (543 packages), ares-package built the IPK without error, ares-p… **Errors:** none. The `webos-service` npm module is proprietary (LG SDK) and unavailable on public … **Verification:** frontend JS executed end-to-end in mock browser context (all 6 files in dependenc…
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 3 minutes, faster than the median of the 8 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- Licensed MPL-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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.
Of the 9 jellyfin projects Argusic has installed and timed, jellyfin-webos was the 4th fastest to reach a running state, and 5 of 9 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 | 2/3 | Unverified | 80.00 | 0.01 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.04 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jellyfin-webos)Questions
- Does jellyfin-webos run?
- jellyfin-webos runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test jellyfin-webos?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ab4794046467. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test jellyfin-webos?
- 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 jellyfin-webos 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 jellyfin-webos need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing jellyfin-webos?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does jellyfin-webos compare with the alternatives?
- Of the 9 jellyfin projects Argusic has installed and timed, jellyfin-webos was the 4th fastest to reach a running state, and 5 of 9 reached one at all.
- Where is the evidence for jellyfin-webos?
- 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.