tonzhon-music
铜钟「Tonzhon」: 干净纯粹的音乐平台 (铜钟已不再使用原来的 tonzhon.com，现在的 tonzhon.com 不是正版的铜钟)
Runs with mockssource: GitHubhomepageJavaScriptMITcommit 764bd60c60c5
JavaScript, MIT licensed. The project labels itself: antd, music, music player, react, react router, tonzhon and webapp.
tonzhon-music runs, with stand-ins for the services it depends on. An Argusic agent installed it in 6 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Tonzhon music web app builds with npm run build (551ms, 12 output assets), serves via npm run dev (Vite 8, 200 on /), proxies all /api endpoints to a custom mock server that returns realistic JSON for hot-songs, search, song-playback, and favorites endpoints.
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 92 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.
- Backend API host tonzhon.whamon.com does not resolve in DNS5 minutes
- Node.js v18 too old (needs >=20.19)3 minutes
- @rolldown/binding-linux-x64-gnu native binding missing (npm install ran under Node 18)1 minute
- manualChunks object type not supported by Vite 8/rolldown (must be function)1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl http://localhost:5173/ returned 200; curl http://localhost:5173/api/hot-songs returned valid mock JSON; curl http://localhost:5173/api/search?provider=spotify&keyword=test&page=1 returned valid mock JSON; curl http://localhost:5173/api/p/song-1 returned valid mock JSON; npm run build exited 0 producing 12 assets in 551ms; npm run preview served the built app at http://localhost:4173/ with working API proxy
- Model tokens used
- 125,588
- Exact commit tested
- 764bd60c60c5
- 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.
exec /bin/sh -lc "which chromium chromium-browser google-chrome firefox 2>/dev/null; ls /usr/bin | grep … succeeded in 0ms: no playwright cache No browser in container. The project is a frontend SPA that depends on a backend API. I've verified… exec /bin/sh -lc "pkill -f 'mock-server' 2>/dev/null; pkill -f 'vite' 2>/dev/null; pkill -f 'node.*previ… exited 143 in 0ms: Now let me compile the final result. Here's a summary of everything I found: tokens used 125,588 Now let me compile the final result. Here's a summary of everything I found:
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 6 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
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.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.08 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/tonzhon-music)Questions
- Does tonzhon-music run?
- tonzhon-music runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 6 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test tonzhon-music?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 764bd60c60c5. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test tonzhon-music?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does tonzhon-music 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 tonzhon-music need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing tonzhon-music?
- 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.
- Where is the evidence for tonzhon-music?
- 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.