beatify
🎵 Music quiz party game for Home Assistant with two modes, guess the release year or name the title and artist. Streams from Spotify, Apple Music, Tidal, Deezer, YouTube Music and Amazon Music, or plays your own library via Plex, Jellyfin and local files. Runs on Sonos, Alexa and any Music Assistant speaker.
Runssource: GitHubhomepagePythonMITcommit 4369d58ca542
Python, MIT licensed. The project labels itself: alexa, hacktoberfest, hacs, home assistant, home assistant custom component, home automation, music assistant and music quiz.
beatify runs. An Argusic agent installed it in 1.5 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 venv installed, 3032 of 3034 pytest tests pass, ruff lint and mypy type-check are clean, frontend build artifacts are verified, npm packages installed with engine warnings only.
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.
- Vitest requires Node.js >=22, container has v18
- Install time
- 2 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- pytest tests/ exited 0: 3032 passed, 2 skipped
- Model tokens used
- 30,276
- Exact commit tested
- 4369d58ca542
- 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.
/bin/sh -lc 'cd /work/repo && node scripts/build.mjs --help 2>&1 || head -50 scripts/build.mjs' in … succeeded in 186ms: ✅ built 16 artifacts, 83 .gz siblings Now I have a complete picture. Let me check whether the build created any new artifacts: exec /bin/sh -lc 'cd /work/repo && node scripts/build.mjs --check 2>&1' in /work/repo succeeded in 58ms: ✅ all 16 artifacts and 83 .gz siblings match source Everything works. Here's the full report: tokens used 30,276 Everything works. Here's the full report:
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 1.5 minutes.
- 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.
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 1.5 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)
alexahacktoberfesthacshome-assistanthome-assistant-custom-componenthome-automationmusic-assistantmusic-quizmusic-triviaparty-gamepythonqr-codesmart-homesonostrivia-game
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/beatify)Questions
- Does beatify run?
- Yes. beatify runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test beatify?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4369d58ca542. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test beatify?
- 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 beatify take to install?
- 1.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 beatify need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing beatify?
- 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.
- Where is the evidence for beatify?
- 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.