autopulse

💫 automated lightweight service that updates media servers like Plex and Jellyfin based on notifications from media organizers like Sonarr and Radarr

Runssource: GitHubhomepageRustMITcommit 6c98b6beda76

Rust, MIT licensed. The project labels itself: autoscan, emby, jellyfin, plex and servarr.

autopulse runs. An Argusic agent installed it in 5.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

autopulse v2.0.0 builds from source with all vendored dependencies, all 192 tests pass, and the HTTP server starts and correctly processes API requests with SQLite on localhost:2875.

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
1
last tested
stars
556
forks
17
open issues
9
watchers
5
size
3 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.

Install time
6 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cargo test --workspace --features vendored exited 0, 192 passed, 2 ignored (postgres-only). Server launched and returned HTTP 200 on root, /stats, and manual trigger endpoints.
Model tokens used
166,395
Exact commit tested
6c98b6beda76
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

tokens used
166,395
Let me compile my final assessment. Here's a summary of everything done and observed:
**Install**: Installed Rust via rustup, then `cargo build --features vendored` succeeded cleanly. N…
**Build**: Full workspace compiled in ~2m 4s on the first pass. Rust 1.99.1, no errors.
**Tests**: `cargo test --workspace --features vendored` ran 192 tests across 4 crates — all passed …
**Launch**: The server started on `127.0.0.1:2875` with a minimal config (SQLite, default auth). Ve…
- `GET /` → HTTP 200, `{"autopulse":"6c98b6b"}`
- `GET /stats` (with basic auth) → HTTP 200, `{"stats":{"total":0,...,"pending":0},"speed":0.316}`
- `POST /triggers/manual?path=/test/file.mkv&event=manual` → HTTP 200, created a scan event with a …
- `POST /triggers/manual` with JSON body → correctly rejected with HTTP 400 "Invalid request"
- `GET /api/config-template` → returned a full TOML config template with HTTP 200

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.
  • Installed in 5.5 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • 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

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 5.5 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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.03

Topics (from GitHub)

autoscanembyjellyfinplexservarr

Embed the badge

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

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

Questions

Does autopulse run?
Yes. autopulse runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test autopulse?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6c98b6beda76. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test autopulse?
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 autopulse take to install?
5.5 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 autopulse need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing autopulse?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for autopulse?
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