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 22 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Built production bundle (12 assets) and served via vite dev server with mock API backend; frontend serves index.html, API responds with mock data on all 4 endpoint patterns.
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.
- Real backend tonzhon.whamon.com unreachable5 minutes
- Node.js v18.19.1 too old for Vite 8 (requires >=20.19 or >=22.12)2 minutes
- manualChunks config as object rejected by Rolldown in Vite 82 minutes
- npm install with old Node left broken native bindings for @rolldown/binding1 minute
- vite.config.js loaded as CommonJS but uses ESM syntax1 minute
- __dirname not supported by Vite 8 native config loader1 minute
- Install time
- 22 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- curl http://localhost:5173/ returned HTTP 200; curl http://localhost:5173/api/hot-songs returned JSON with 5 songs; curl http://localhost:5173/api/search?provider=spotify&keyword=test returned paginated results; npm build exited 0
- Model tokens used
- 64,601
- 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
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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.
| # | Error | Fix | |---|-------|-----| | 1 | **Node.js v18.19.1 is too old** — Vite 8 requires Node >= 20.19 or >= 22.12 | Downloaded Node… | 2 | **npm install with old Node leaves broken native bindings** — `npm i` succeeded but `npm run … | 3 | **`vite.config.js` loaded as CommonJS but uses ESM** — warning and eventual error from Rolldo… | 4 | **`manualChunks` must be a function in Rolldown** — Vite 8 uses Rolldown which rejects the ob… | 5 | **`__dirname` not supported by native config loader** — import.meta.dirname is the replacemen… | 6 | **Real backend `tonzhon.whamon.com` unreachable** — API requests return nothing | Created `mo… ## Verification - **Build** (`npm run build`): succeeded, producing 12 output assets (JS, CSS, HTML) - **Dev server** (`npm run dev`): starts on `localhost:5173`, returns HTTP 200 on `/` - **Mock API**: tested all 4 endpoint patterns (`/api/hot-songs`, `/api/search`, `/api/p/*`, `/api/…
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 22 minutes.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, 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.
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 | Runs with mocks | 92.00 | 0.05 | |
| 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 22 minutes, hitting 6 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. 2 attempts are 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.05: 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?
- 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 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?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for tonzhon-music?
- 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.