watchstate
Self-hosted service to sync your plex, jellyfin and emby play state. without relying on 3rd-party external services.
Runssource: GitHubPHPMITcommit 23a7fb2eff8f
PHP, MIT licensed. The project labels itself: backup, docker, emby, jellyfin, matched, misidentified, mismatched and plex.
watchstate runs. An Argusic agent installed it in 22 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
WatchState (FrankenPHP 1.13.0 / PHP 8.5.11) installed with composer dependencies; HTTP server launches and healthcheck endpoint returns 200 OK; 905 of 907 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 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.
- FrankenPHP v1.13.0 php-cli does not support -v flag and requires .php file extension for scripts - non-.php scripts like bin/console are interpreted as Caddy subcommands10 minutes
- 2 WorkerCommandTest failures: test_incomplete_session and test_child_command - subprocess spawn via bin/console shebang fails with frankenphp php-cli5 minutes
- Yaml::parseFile returns null on empty files, causing array_replace_recursive TypeError on first HTTP request2 minutes
- in_container() returns true due to /.dockerenv, making Config::get(path) default to /config instead of WS_DATA_PATH2 minutes
- Install time
- 22 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl -s http://localhost:8199/v1/api/system/healthcheck returned 200 with {"status":"ok","message":"System is healthy"}; phpunit ran 907 tests with 3765 assertions
- Model tokens used
- 212,797
- Exact commit tested
- 23a7fb2eff8f
- 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.
**Verification:**
- `frankenphp php-server` launched on `localhost:8199` - **healthcheck returned HTTP 200** with `{"…
- **phpunit ran 907 tests, 3765 assertions** - 905 passed, 2 failed
### 4 errors encountered and fixed
| Error | Fix |
|---|---|
| FrankenPHP php-cli requires `.php` extension; non-`.php` scripts (e.g. `bin/console`) treated as …
| Empty YAML config files cause `Yaml::parseFile` to return null → `TypeError` on boot | Filled wit…
| `/.dockerenv` exists → `in_container()` returns true → config paths default to `/config` | Set `I…
| 2 worker subprocess tests fail (Symfony Process can't find `php` via shebang) | Requires `php` on…
### Results
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 22, "e…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 4 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 MIT, as reported by its host.
What did not, or is not known
- Took 22 minutes to install, slower than the median of the 19 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 20 backup projects Argusic has installed and timed, watchstate was the 15th fastest to reach a running state, and 14 of 20 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
Topics (from GitHub)
backupdockerembyjellyfinmatchedmisidentifiedmismatchedplexwatchstatewebhook
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/watchstate)Questions
- Does watchstate run?
- Yes. watchstate runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test watchstate?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 23a7fb2eff8f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test watchstate?
- The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does watchstate take to install?
- 22 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 watchstate need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing watchstate?
- 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 watchstate compare with the alternatives?
- Of the 20 backup projects Argusic has installed and timed, watchstate was the 15th fastest to reach a running state, and 14 of 20 reached one at all.
- Where is the evidence for watchstate?
- 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.